From 4c7b68aae446d4394cb070e0c287f821aa335e5c Mon Sep 17 00:00:00 2001 From: Masakazu Kitajo Date: Wed, 7 Feb 2024 10:59:21 -0700 Subject: [PATCH] Deprecate the support for NPN --- doc/admin-guide/configuration/session-protocol.en.rst | 4 +++- doc/developer-guide/api/functions/TSHttpConnectPlugin.en.rst | 2 +- .../api/functions/TSHttpConnectWithPluginId.en.rst | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/admin-guide/configuration/session-protocol.en.rst b/doc/admin-guide/configuration/session-protocol.en.rst index cffab34caf0..3f38e5f3961 100644 --- a/doc/admin-guide/configuration/session-protocol.en.rst +++ b/doc/admin-guide/configuration/session-protocol.en.rst @@ -42,7 +42,9 @@ protocols: Each proxy port can be configured in :ts:cv:`proxy.config.http.server_ports` to support a subset of these session protocols. For TLS enabled connections this -configuration controls which protocols are offered by NPN. Protocol sniffing is +configuration controls which protocols are offered by ALPN and NPN. Protocol sniffing is use for non-TLS proxy ports to determine which protocol is being used by the client. If the detected protocol is not supported for that proxy port the connection is dropped. + +Support for NPN is deprecated, and it will be removed on a future release. diff --git a/doc/developer-guide/api/functions/TSHttpConnectPlugin.en.rst b/doc/developer-guide/api/functions/TSHttpConnectPlugin.en.rst index 399da389c09..fe90037f2e5 100644 --- a/doc/developer-guide/api/functions/TSHttpConnectPlugin.en.rst +++ b/doc/developer-guide/api/functions/TSHttpConnectPlugin.en.rst @@ -75,7 +75,7 @@ The H2 implementation uses this to correlate client sessions with H2 streams. Each client connection is assigned a distinct numeric identifier. This is passed in the options structure via the member variable `id` to the :c:func:`TSHttpConnectPlugin` function. -The :arg:`tag` is selected to be the NPN string for the client session +The :arg:`tag` is selected to be the ALPN (or NPN) string for the client session protocol, e.g. "h2". Log post processing can then count the number of connections for the various supported protocols and the number of H2 virtual streams for each real client connection to Traffic Server. diff --git a/doc/developer-guide/api/functions/TSHttpConnectWithPluginId.en.rst b/doc/developer-guide/api/functions/TSHttpConnectWithPluginId.en.rst index 4e5f9274cb0..6f6202c3217 100644 --- a/doc/developer-guide/api/functions/TSHttpConnectWithPluginId.en.rst +++ b/doc/developer-guide/api/functions/TSHttpConnectWithPluginId.en.rst @@ -98,7 +98,7 @@ The H2 implementation uses this to correlate client sessions with H2 streams. Each client connection is assigned a distinct numeric identifier. This is passed as the :arg:`id` to :c:func:`TSHttpConnectWithPluginId`. The :arg:`tag` is selected -to be the NPN string for the client session protocol, e.g. +to be the ALPN (or NPN) string for the client session protocol, e.g. "h2". Log post processing can then count the number of connections for the various supported protocols and the number of H2 virtual streams for each real client connection to Traffic Server.