Ticket #251 (closed design: fixed)
message-body in CONNECT request
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p2-semantics||Severity:||Active WG Document|
I've come across a problem with an HTTP client which sends message bodies and Content-Length when using the CONNECT method.
Is it even legal for a CONNECT command to have a body? If it does, what should the proxy do? The client (a panasonic blue-ray player) breaks if the body is forwarded, however RFC2817 Sec 5.2 last para implies it is legal to have a body here.
Does anyone know of any other client that sends a body on CONNECT and relies on it? It seems very odd to have a body there, since you don't even have a connection necessarily to the end server yet. I'm loath to break the proxy to support a broken client.
- Status changed from new to closed
- Resolution set to incorporated
- Milestone changed from unassigned to 14
- Status changed from closed to reopened
- Resolution incorporated deleted