search

ietf-wg-masque / draft-ietf-masque-quic-proxy

Other
13 stars 7 forks source link

Message bodies #6

Closed LPardue closed 4 years ago

LPardue commented 4 years ago

The spec says:

Body payloads within CONNECT-QUIC requests are undefined, and SHOULD be treated as malformed.

but https://tools.ietf.org/html/draft-ietf-httpbis-semantics-11#section-8.4.2 says

Since message parsing (Section 6 of [Messaging]) needs to be independent of method semantics (aside from responses to HEAD), definitions of new methods cannot change the parsing algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of new methods can specify that only a zero-length message body is allowed by requiring a Content-Length header field with a value of "0".

You might get a question from the HTTP police.

tfpauly commented 4 years ago

Yeah, we should require Content-Length 0.