You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Roy T. Fielding" <fi...@liege.ICS.UCI.EDU> on 1996/07/06 04:04:53 UTC

Re: Apache 1.2 & HTTP/1.1

> Roy's already promised that Apache might be the first HTTP/1.1-compliant
> server, and I think that'd not be a bad thing. It's the first item on
> http://hyperreal.com/httpd/project-plan.html as well.

Ummm, I was just kidding -- I didn't actually promise it.  I'd like it,
but I don't promise things for other people.  I'll be plugged-in this
weekend (ouch), so let me know if anything needs to be clarified
(or if something seems so annoying that you want to force me to code it).

......Roy

Re: Apache 1.2 & HTTP/1.1

Posted by Alexei Kosut <ak...@nueva.pvt.k12.ca.us>.
On Fri, 5 Jul 1996, Roy T. Fielding wrote:

> Ummm, I was just kidding -- I didn't actually promise it.  I'd like it,
> but I don't promise things for other people.  I'll be plugged-in this
> weekend (ouch), so let me know if anything needs to be clarified

Actually... I do need a couple things clarified.

Re Section 3.6. Am I correct in thinking that if a chunked body,
if it has no footers, should end with "0" and two CRLF pairs? Looking
at section 19.4.6, it seems like there might only be one.

Section 4.4 says that multipart/byteranges is an indication of
message length. So does this mean that if I've got a
multipart/byteranges document, I can open a persistent connection
without having a Content-length or chunked transfer-coding? (for that
matter, is it legal to chunk a multipart/byteranges entity?)

Another question regarding multipart/byteranges, if a browser sends:

Range: bytes=-10,30-40,0-5,25-35

am I allowed to send (assuming a 100 byte document) back in a
multipart/byteranges:

Content-range: bytes 0-5/100
Content-range: bytes 25-40/100
Content-range: bytes 89-99/100

i.e. can I mix the order around and merge overlapping ranges? I sure
as heck hope the answer is yes. (if not, I hope someone will tell me
how I'm supposed to serve up a byterange of a dynamically generated
document without caching the whole thing first, which for very large
documents could prove prohibitive.)

Thanks.

-- 
________________________________________________________________________
Alexei Kosut <ak...@nueva.pvt.k12.ca.us>      The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/   http://www.apache.org/