From 85898ee59e81d9703f43e5567a39775b22274075 Mon Sep 17 00:00:00 2001 From: Ben Schwartz Date: Tue, 22 Oct 2024 11:35:13 -0400 Subject: [PATCH] [connect-tcp] Typo --- draft-ietf-httpbis-connect-tcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-connect-tcp.md b/draft-ietf-httpbis-connect-tcp.md index 5dd023efa..797b1ff69 100644 --- a/draft-ietf-httpbis-connect-tcp.md +++ b/draft-ietf-httpbis-connect-tcp.md @@ -147,7 +147,7 @@ Clients SHOULD assume that all proxy resources generated by a single template sh ## Use of the Capsule Protocol {#capsule-protocol} -When using the "connect-tcp" Upgrade Token, templated TCP proxies do not use the Capsule Protocol {{!RFC9297}}. Clients MAY request use of the Capsule Protocol by offering the Upgrade Token "connect-tcp-capsule" instead. When offering or accepting the "connect-tcp-capsule" Upgrade Token, clients and servers SHOULD including a "Capsule-Protocol: ?1" header to facilitate processing by intermediaries. +When using the "connect-tcp" Upgrade Token, templated TCP proxies do not use the Capsule Protocol {{!RFC9297}}. Clients MAY request use of the Capsule Protocol by offering the Upgrade Token "connect-tcp-capsule" instead. When offering or accepting the "connect-tcp-capsule" Upgrade Token, clients and servers SHOULD include a "Capsule-Protocol: ?1" header to facilitate processing by intermediaries. Clients of this specification MAY implement "connect-tcp", "connect-tcp-capsule", or both. Accordingly, a templated TCP proxy server MUST implement both Upgrade Tokens unless its use is restricted to a subset of compatible clients.