* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #250 (closed design: fixed)

Opened 4 years ago

Last modified 23 months ago

message-body in CONNECT response

Reported by: mnot@pobox.com Owned by: fielding@gbiv.com
Priority: normal Milestone: 19
Component: p2-semantics Severity: Active WG Document
Keywords: CONNECT,body Cc:
Origin: http://www.w3.org/mid/474B1CD6.80101@gmail.com

Description

As implemented in the real world, a successful response to a CONNECT request does not include a message-body. But this isn't stated in RFC 2817, and is actually forbidden by RFC 2616.

draft-luotonen-web-proxy-tunneling said:

Example of a response:

HTTP/1.0 200 Connection established Proxy-agent: Netscape-Proxy/1.1

...data tunnelled from the server...

After the empty line [that follows the message-headers], the proxy will start passing data from the client connection to the remote server connection

but RFC 2817 (5.3) removes the lack-of-message-body implication:

Any successful (2xx) response to a CONNECT request indicates that the proxy has established a connection to the requested host and port, and has switched to tunneling the current connection to that server connection.

Change History

comment:1 Changed 3 years ago by mnot@pobox.com

  • Owner set to fielding@gbiv.com

Roy: Special-case CONNECT responses to indicate that if there's no Content-Length, the termination of the header fields indicates tunnelling has begun.

comment:2 Changed 3 years ago by dan.winship@gmail.com

suggested text:

Note: Most existing implementations of CONNECT treat successful (2xx) responses to CONNECT requests as intrinsically having no message-body (ie, like responses to HEAD). For compatibility, servers SHOULD NOT include a non-empty message-body in a successful CONNECT response, and clients SHOULD treat a successful CONNECT response with no Content-Length or Transfer-Encoding headers as having no message-body.

comment:3 Changed 3 years ago by fielding@gbiv.com

  • Keywords CONNECT,body added
  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 19

Incorporated in [1570].

comment:4 Changed 3 years ago by julian.reschke@gmx.de

From [1572]:

Note change for [1570] (see #250)

comment:5 Changed 2 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:6 Changed 2 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed

comment:7 Changed 23 months ago by julian.reschke@gmx.de

From [1973]:

Mention CONNECT special-case in Changes from 2616 (see #250)

Note: See TracTickets for help on using tickets.