[
https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570183#comment-14570183
]
James Peach commented on TS-3476:
---------------------------------
I disagree with the premise here. We should be logging the application
protocol, not the TLS negotiated protocol.You can do SPDY and HTTP/2 on plain
old TCP as well as protocol plugins. You don't need the stored APLN/NPN
information because what matters is the concrete class that handles the
protocol, which is the ProxyClientSession subclass.
> Add a log tag for APLN/NPN negotiated protocol
> ----------------------------------------------
>
> Key: TS-3476
> URL: https://issues.apache.org/jira/browse/TS-3476
> Project: Traffic Server
> Issue Type: New Feature
> Components: Logging, SSL
> Reporter: Leif Hedstrom
> Assignee: Eric Schwartz
> Fix For: 6.0.0
>
>
> It seems crucial to be able to log which protocol handler was negotiated with
> ALPN (and perhaps NPN as long as we support it). This could simple be the
> string that was negotiated by the client/server in the TLS handshake. For
> example, with HTTP/2, it would be "h2" (or "h2-14" with some browsers).
> A suggested log tag name would be %<alpn> which seems clear enough to me and
> easy to remember :).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
