Robert Brewer ha scritto:
> Chris Withers wrote:
>> Manlio Perillo wrote:
>>> 2) handle the range request in the WSGI application.
>>>    Its not hard as long as you do not implement multiple ranges
>> support.
>>>    If your object database supports seeks, this should be the most
>>>    efficient solution.
>> This is probably what's wanted. So, if a wsgi app does its own range
>> handling, the wsgi server won't interfere?
> 
> Apache will interfere, and try to re-apply the range to whatever you
> emit. The only solution we've found so far is to tell the app to ignore
> any 'Range' request header when running behind Apache, and just let
> Apache have its way. See http://www.cherrypy.org/changeset/1319
> 

Strange, looking at the byterange filter source code (from trunk) it 
seems that Apache first checks if content is already a single or 
multiple range
(searching  for Content-Range and Content-Type = "multipart/byteranges 
in in headers_out)

> 
> Robert Brewer
> [EMAIL PROTECTED]
> 


Manlio Perillo
_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: 
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com

Reply via email to