message-body in CONNECT response
|Reported by:||mnot@…||Owned by:||fielding@…|
|Component:||p2-semantics||Severity:||Active WG Document|
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.
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 (7)
comment:3 Changed 5 years ago by fielding@…
- Keywords CONNECT body added
- Milestone changed from unassigned to 19
- Resolution set to incorporated
- Status changed from new to closed
comment:5 Changed 5 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:6 Changed 5 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed