- From: Alex Rousskov <rousskov@measurement-factory.com>
- Date: Thu, 27 May 2004 11:18:03 -0600 (MDT)
- To: patrick mcmanus <mcmanus@ducksong.com>
- Cc: Jamie Lokier <jamie@shareable.org>, HTTP working group <ietf-http-wg@w3.org>
On Thu, 27 May 2004, patrick mcmanus wrote: > On Thu, 2004-05-27 at 12:49, Alex Rousskov wrote: > > On Thu, 27 May 2004, patrick mcmanus wrote: > > > > > > Does announcing HTTP/1.1 actually buy you anything at all? > > > > It can get you chunked responses.. > > > > ... and can messages with HTTP/1.0 version strings and TE: chunked. > > HTTP/1.0 with TE: chunked cannot safely cause a chunked response. That > combination is much more likely to be a HTTP/1.0 proxy that propogated a > TE header it didn't know was hop-to-hop. There is a real chance that > proxy won't be able to interpret the response correctly. Oof. I should have been more careful when writing HTTP header names. Sorry. What I meant to say is that it is safe to respond with chunked HTTP/1.0 response to an HTTP/1.1 request: GET / HTTP/1.1 ... HTTP/1.0 200 OK Transfer-Encoding: chunked ... You are absolutely right that TE request-header has nothing to do with the ability to use chunking with HTTP/1.0 messages. Alex.
Received on Thursday, 27 May 2004 13:18:09 UTC