[
https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648638#comment-14648638
]
ASF subversion and git services commented on TS-3476:
-----------------------------------------------------
Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch
refs/heads/6.0.x from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ]
Merge branch 'master' into 6.0.x
* master:
TS-3807: Remove legacy log splitting code and docs.
TS-3749: Re-enable error log.
TS-3492 Only send SETTINGS which are different than protocol defaults
TS-3766 Ignore unknown frame in debugging
[TS-3476] Add a log tag for application protocol (add docs)
Revert "TS-3752: Problem with larger headers and HTTP/2"
TS-3800: Fix bug in hostdb ui related to missing query
TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800)
> 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)
