You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: draft-ietf-httpbis-connect-tcp.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,14 +82,14 @@ In HTTP/1.1, the client uses the proxy by issuing a request as follows:
82
82
* The request SHALL include a single "Host" header field containing the origin of the proxy.
83
83
* The request SHALL include a "Connection" header field with the value "Upgrade". (Note that this requirement is case-insensitive as per {{Section 7.6.1 of !RFC9110}}.)
84
84
* The request SHALL include an "Upgrade" header field with the value "connect-tcp".
85
-
* The request SHOULD include a "Capsule-Protocol: ?1" header.
85
+
* The request SHOULD include a "Capsule-Protocol: ?1" header (as recommended in {{!RFC9297, Section 3.4}}).
86
86
87
87
If the request is well-formed and permissible, the proxy MUST attempt to establish the TCP connection before sending any response status code other than "100 (Continue)" (see {{conveying-metadata}}). If the TCP connection is successful, the response SHALL be as follows:
88
88
89
89
* The HTTP status code SHALL be "101 (Switching Protocols)".
90
90
* The response SHALL include a "Connection" header field with the value "Upgrade".
91
91
* The response SHALL include a single "Upgrade" header field with the value "connect-tcp".
92
-
* The response SHOULD include a "Capsule-Protocol: ?1" header.
92
+
* The response SHOULD include a "Capsule-Protocol: ?1" header (as above).
93
93
94
94
If the request is malformed or impermissible, the proxy MUST return a 4XX error code. If a TCP connection was not established, the proxy MUST NOT switch protocols to "connect-tcp", and the client MAY reuse this connection for additional HTTP requests.
95
95
@@ -122,6 +122,8 @@ In HTTP/2 and HTTP/3, the proxy MUST include SETTINGS_ENABLE_CONNECT_PROTOCOL in
122
122
123
123
A templated TCP proxying request that does not conform to all of these requirements represents a client error (see {{!RFC9110, Section 15.5}}) and may be malformed (see {{Section 8.1.1 of !RFC9113}} and {{Section 4.1.2 of !RFC9114}}).
124
124
125
+
Additionally the "capsule-protocol" header field SHOULD be present with a value of "?1" (as recommended in {{!RFC9297, Section 3.4}}).
0 commit comments