[
https://issues.apache.org/jira/browse/TS-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735073#comment-14735073
]
ASF GitHub Bot commented on TS-3648:
------------------------------------
GitHub user ericcarlschwartz opened a pull request:
https://github.com/apache/trafficserver/pull/288
[TS-3648] Desire support for client TLS cipher in custom log format
We had a crash at y! related to this change. Here are our fixes from myself
and @SolidWallOfCode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ericcarlschwartz/trafficserver ts-3648
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/288.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 #288
----
commit 1e5a599e45c9142e552799bf81ea076055f6dd64
Author: Eric Schwartz <[email protected]>
Date: 2015-09-08T14:38:44Z
[TS-3648] Desire support for client TLS cipher in custom log format
----
> Desire support for client TLS cipher in custom log format
> ---------------------------------------------------------
>
> Key: TS-3648
> URL: https://issues.apache.org/jira/browse/TS-3648
> Project: Traffic Server
> Issue Type: New Feature
> Components: Logging
> Reporter: Eric Sproul
> Assignee: Eric Schwartz
> Fix For: 6.1.0
>
>
> While the TLS cipher stats from TS-2169 are awesome for seeing what ciphers
> are in active use, I would also like to be able to create a custom log to
> track cipher by client request. That would enable me, for example, to
> determine who among my users might be affected by a cipher list change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
