[
https://issues.apache.org/jira/browse/TS-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603251#comment-14603251
]
Eric Schwartz commented on TS-3648:
-----------------------------------
looking at [~acacio]'s PR it looks like there was one change requested. as this
is now assigned to me I can make that edits to his PR and open a new PR if he's
no longer working on this?
or do we want to go a different way with this? i agree with some of the
commentary about not adding new fields to HttpSM every time we need to update
log fields. there was some discussion of creating a separate logging substruct
in HttpSM. i could also take that on if this and a couple of [~fpesce]'s PRs
are reviewed and merged and we like that idea.
> 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)
