W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Re: Proposal: 205 Bodies [#88]

From: Adrien de Croy <adrien@qbik.com>
Date: Tue, 26 Oct 2010 11:06:18 +1300
Message-ID: <4CC5FF5A.40702@qbik.com>
To: Daniel Stenberg <daniel@haxx.se>
CC: Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>

I guess the confusing issue is what is the purpose or meaning of a body 
on a CONNECT request message?  What should a proxy do with it?  The only 
case I've seen, the only thing that worked was discarding the body.  So 
WinGate now discards all bodies on CONNECT requests.

If they are supposed to be forwarded after the connection is made, then 
the message would need to be completed before this is done, so if 
chunked, a 0 chunk would have to have been received.

I imagine it's fairly common to get chunked bodies on 407 response 
messages regardless of the request method.

So I guess I take it back about whether chunking should be allowed, but 
I still suggest bodies should be disallowed.

The other non-standard thing about CONNECT is the reusability of the 
connection, and connection state management.  For instance, is it 
required for all successful responses to CONNECT to specify Connection: 
close? Since that's the only way to specify that the connection cannot 
be used for anything else afterwards, which we all know is actually the 
case, since HTTP framing is lost as soon as the response message is 
completed.




On 26/10/2010 10:54 a.m., Daniel Stenberg wrote:
> On Tue, 26 Oct 2010, Adrien de Croy wrote:
>
>> Can we allow Transfer-Encoding: chunked on CONNECT?  IMO we can't.
>
> Why not? I've seen proxies respond with chunked CONNECT responses (for 
> 407 bodies).
>
Received on Monday, 25 October 2010 22:06:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:30 GMT