[
https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571426#comment-14571426
]
Eric Schwartz commented on TS-3476:
-----------------------------------
As far as I know, there isn't an existing path from the HttpSM back to the
ProxyClientSession currently in the code. (If I'm wrong here, please let me
know)
Was looking into adding one by associating the HttpClientSession (ua_session)
w/ its "parent" ProxyClientSession in FetchSM. However I could only access it
toward the end of FetchSM's life cycle, in the final call to process_fetch_read.
The path I found was through the PluginVC's read_state. Is there a way to
access the underlying HttpClientSession earlier in FetchSM that anyone knows of?
> Add a log tag for application 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)
