[
https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740095#comment-14740095
]
ASF GitHub Bot commented on TS-3476:
------------------------------------
GitHub user masaori335 opened a pull request:
https://github.com/apache/trafficserver/pull/290
[TS-3476] Fix typo in docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/masaori335/trafficserver ts-3683
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/290.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 #290
----
commit 0f9b6d97fb58bea8c81aab69d169bc729fc3ab83
Author: Masaori Koshiba <[email protected]>
Date: 2015-09-11T03:15:13Z
[TS-3476] Fix typo in 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.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)
