This was a bug in my head(which seems to be the source of most of them). I should have known better than to run off on a wild header case goose chase. My web development work has been infrequent the last few years. I'm guessing from JJ's response he's wondering what I'm up to with this funkyheader :) ? I have some large files 500MB+ I serve out of an app running pylons behind lighttpd. My access control/meta data/versioning code is over in pylons but but serving files that size via proxy or fastcgi has been bad. The header X-LIGHTTPD-send-file: /Users/kai/Documents/vimbook-OPL.pdf is an instruction to lighttpd to toss the body of the response returned by the upstream server (pylons in this case) and instead serve the file from disk. This sped things way up for me. The source of the problem ended up being that I needed to send a content length or lighttpd refused to take action on the header. It didn't matter what I set the value of the header to be as long as I set it to a number (-1, 536870912, ... ). Sorry this is not very pylons related but I figured someone serving large files from a pylons/wsgi app might find this info useful.
Kai --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
