This is an automated email from the ASF dual-hosted git repository. cmcfarlen pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/trafficserver.git
commit 8288cedcae65599edaa9079ff9948d1a77c12372 Author: Brian Neradt <[email protected]> AuthorDate: Wed Apr 16 15:44:47 2025 -0500 doc: ssl.client.alpn_protocol h22o update (#12190) ssl.client.alpn_protocol was added before HTTP/2 to origin was supported and the "h2" examples stated the lack of support. But now that we support HTTP/2 to origin since 10.x, the docs should be updated to remove the statement that HTTP/2 to origin is not supported. (cherry picked from commit 1f78f5d595e2484ceaf7fc9730eeaa88ac137624) --- doc/admin-guide/files/records.yaml.en.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/admin-guide/files/records.yaml.en.rst b/doc/admin-guide/files/records.yaml.en.rst index abc339eb56..3a544064e3 100644 --- a/doc/admin-guide/files/records.yaml.en.rst +++ b/doc/admin-guide/files/records.yaml.en.rst @@ -4294,10 +4294,9 @@ Client-Related Configuration ``"h2,http/1.1,http/1.0"`` HTTP/2 is preferred by |TS| over HTTP/1.1 and HTTP/1.0. Thus, if the origin supports HTTP/2, it will be used for the connection. If not, it will fall back to HTTP/1.1 or, if that is not supported, - HTTP/1.0. (HTTP/2 to origin is currently not supported by |TS|.) + HTTP/1.0. ``"h2"`` |TS| only advertises HTTP/2 support. Thus, the origin will - either negotiate HTTP/2 or fail the handshake. (HTTP/2 to origin - is currently not supported by |TS|.) + either negotiate HTTP/2 or fail the handshake. ================================ ====================================================================== Note that this is an overridable configuration, so the ALPN can be configured on a per-origin
