GitHub user ericcarlschwartz opened a pull request:

    https://github.com/apache/trafficserver/pull/194

    Ts 3534

    Initial pull request for wiretracing v0. Please leave me your comments and 
I'll make changes as necessary.
    
    Looking into this now: Making sure we turn tracing off for all connections 
when we return them to the pool Sudheer pointed this out to me.
    
    Any other input would be greatly appreciated. Some of the feedback from the 
summit was passed on to me but would always be happy to hear more again. I know 
there was discussion of refactoring some of this. I also know there was 
discussion of outputting pcap files instead of traces to a log. <- this one 
might be hard because the traces are based on what's read from the buffers and 
not on the individual packets. if someone could point me to code where i could 
get that kind of granularity that would be a cool enhancement.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yahoo/trafficserver TS-3534

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/194.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 #194
    
----
commit d1c4be46ce8ee725c9709b261e850491b00dea9d
Author: es <e...@yahoo-inc.com>
Date:   2014-10-02T19:27:56Z

    TS-3534 Wiretracing SSL Connections
    
    Initial Commit

commit 5a2e43cb79bef904b80a1736112c94c1451f0c53
Author: es <e...@yahoo-inc.com>
Date:   2015-04-27T23:04:37Z

    TS-3534 Cleanup before PR

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to