[
https://issues.apache.org/jira/browse/TS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622190#comment-14622190
]
ASF subversion and git services commented on TS-3534:
-----------------------------------------------------
Commit 6e3ce5022d67a9c4098595d3d45e24a3c697c80c in trafficserver's branch
refs/heads/master from [~es]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=6e3ce50 ]
TS-3534: Wiretracing SSL Connections. This closes #246.
> Wiretracing for SSL connections
> -------------------------------
>
> Key: TS-3534
> URL: https://issues.apache.org/jira/browse/TS-3534
> Project: Traffic Server
> Issue Type: New Feature
> Components: Logging, Tools
> Reporter: Eric Schwartz
> Assignee: Eric Schwartz
> Fix For: 6.1.0
>
>
> Opening a ticket for discussion of the wiretracing change I made on our
> internal version of ATS.
> The change allows for tracing requests through ATS for: a small percentage of
> traffic, traffic from a certain IP and/or traffic to a specific origin. These
> settings can be combined.
> The main updates are to SSLNetVConnection and UnixNetVConnection (adding the
> trace logic) and to the Logging APIs (to add the special trace logs). One
> change is made to HttpSM to allow client and server traces to be associated
> with one another.
> [~dcarlin] has some notes from the summit on the initial discussion.
> I'll add a pull request with actual code for people to look at shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)