They wouldn't report a different size (all other headers are preserved),
but the header gives the file a fast-track through the web-server and
operating system. Essentially, it tells the OS to stream the file to
the socket, on OS's that support it.
Sean
john muhl wrote:
i've been using the old x-sendfile patch on nginx and mongrel for about a
year with no blank page issues. after setting up an edge 0.7 in a virtual
machine i was able to run nginx and thin in production mode with no blank
pages in well over a million requests through ab (assuming those blank pages
would report their size differently than the page that was supposed to be
served).
On Mon, Feb 2, 2009 at 9:10 PM, Sean Cribbs <[email protected]> wrote:
I got blank pages occasionally until I installed mod_xsendfile properly.
Then, It Just Worked(tm).
Sean
Jason Garber wrote:
And did it work in production? When I did exactly that (probably 4 months
ago), I found sometimes I would get a blank page or the plain text version
of the cache file. I didn't have time to figure it out, so I just turned it
off again.
On Feb 2, 2009, at 4:50 PM, Sean Cribbs wrote:
Jason,
This doesn't affect page_attachments. For Apache, I compiled and
installed mod_xsendfile, and then added these two directives to my Apache
config:
XSendfile on
XSendFileAllowAbove on
And this line to config/environment.rb, inside the after_initialize
block:
ResponseCache.defaults[:use_x_sendfile] = true
Sean
Jason Garber wrote:
Sean, did you use my page_attachments_xsendfile extension? If not, I'm
curious how you set it up.
Jason
On Jan 30, 2009, at 1:23 PM, Sean Cribbs wrote:
Last night at our little hack session at John's, I added the ability to
support X-Accel-Redirect headers for nginx. It would be great if someone
could test this addition with nginx. In config/environment.rb, put this
line inside the config.after_initialize block:
ResponseCache.defaults[:use_x_accel_redirect] = true
Since I have seancribbs.com running the latest and hosted using
Apache/Passenger, I decided to turn on X-Sendfile headers. However, Apache
doesn't seem to recognize them and just serves up a blank response (with the
X-Sendfile header included in the response). So my questions are two:
1) Is this just a side-effect of using Passenger? Would a proxy
scenario (Mongrel, Thin, etc) work?
2) Is there something different Radiant should be doing with other
headers to make it work?
Additionally, if anyone could look into conditional GETs and make sure
we're doing it right, that would be great.
Sean
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
