[
https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625614#comment-14625614
]
ASF GitHub Bot commented on TS-3476:
------------------------------------
GitHub user ericcarlschwartz opened a pull request:
https://github.com/apache/trafficserver/pull/250
[TS-3476] Add a log tag for application protocol (add docs)
Needed to add to the docs for TS-3476
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ericcarlschwartz/trafficserver TS-3476-doc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/250.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #250
----
commit 9a9f06bdcb40cd3b8d5d77058310939eb09578f6
Author: ericcarlschwartz <[email protected]>
Date: 2015-07-14T00:13:22Z
[TS-3476] Add a log tag for application protocol (add docs)
----
> 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.1.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)
