search

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

Other
12 stars 7 forks source link

Non HTTP/3 proxies handling of the method #5

Closed LPardue closed 3 years ago

LPardue commented 3 years ago

The spec says:

The CONNECT-QUIC method as defined in this document can only be supported by an HTTP/3 proxy. Use of CONNECT-QUIC with older HTTP versions is undefined and MUST be rejected.

But RFC7231 says:

When a request method is received that is unrecognized or not implemented by an origin server, the origin server SHOULD respond with the 501 (Not Implemented) status code.

Just checking the two statements are compatible.

tfpauly commented 3 years ago

Yeah, we should just have the 501 behavior