httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51878] 2.2.21 is not compliant for byterange 0- returning 200 instead of 206
Date Wed, 05 Oct 2011 20:08:29 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51878

--- Comment #8 from galt@soe.ucsc.edu 2011-10-05 20:08:29 UTC ---
Just to make the point, if the client software asks for x,y,z,
but apache returns w (even if technically w is a superset of x,y,z),
then the client will know what to do with w.

The way we use apache here is for random access to huge files,
often 180GB or larger. We sure as heck don't want the whole file back.
We usually read the header block (request 1), which tells 
where to find the index (request 2), which tells us were 
to jump to in the data (request 3).  Of course we cache things.
We do not ask for multiple blocks at once.

With some formats, we are able to determine in advance how
much we are reading, but with others we do not know ahead of 
time when we will stop reading, so that the range end is unknown.

Since 200 is what servers that do not support byteranges return,
we reject those servers as soon as we see the header.
It must be 206 to continue.  The fact that there is just one 
case where the part is equal to the whole, does not mean
that we want a 200 instead of a 206.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message