António P. P. Almeida
appa at perusio.net
Wed Sep 26 09:03:13 UTC 2012
On 26 Set 2012 10h17 CEST, nginx-forum at nginx.us wrote:
> Jonathan Matthews Wrote:
>> No. This is a /response/ header from (typically) a dynamic backend
>> which instructs nginx to serve some piece of static content, thus
>> freeing up the backend for more intelligent, heavy-weight request
>> handling. There are more sophisticated uses, but you should at
>> least understand this basic use case before attempting them.
> Hello Jonathan,
> Thanks for the reply. I'd love to at least understand the basics, in
> fact this is what I'm trying to do. It's a bit hard when there's no
> thorough documentation and all responses found on internet are
> You are saying that it will work only when Nginx is a reverse proxy
> and receives a response from another backend, like Apache. But I
> want Apache as frontend and Nginx as backend. Should I focus on
XSendfile in Nginx is called X-Accel-Redirect.
The way X-Accel-Redirect works is that your app/backend sends a
"special" header with the location of the file that is to be served by
Nginx. Usually the application case is for speeding up the delivery of
protected/private files. Let's say you have a ecommerce site that
sells digital downloads. Then these files will be protected and for
speeding up the delivery your application sends an X-Accel-Redirect
header with the location of the file. Then the file is delivered by
Nginx as a regular static file.
Example: I request to download:
The file is stocked at /path/to/the/flac_files/big_hit.flac
your ecommerce sends an header:
when Nginx sees this he knows that now the file is to be served
directly from the file system as a regular static file. Note that the
real location is hidden from the client.
Note that the real location must be protected from direct access by
the client always, be it from your app, be it from your server, for
example using the internal keyword:
In a nutshell that's how it works.
More information about the nginx