You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/07/31 06:02:05 UTC

[jira] [Updated] (TS-3534) Wiretracing for SSL connections

     [ https://issues.apache.org/jira/browse/TS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-3534:
------------------------------
    Fix Version/s:     (was: 6.1.0)
                   6.0.0

> 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.0.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)