[ 
https://issues.apache.org/jira/browse/TS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503276#comment-14503276
 ] 

David Carlin commented on TS-3534:
----------------------------------

Notes I took during my presentation:

* spdy headers compressed
* [~zwoop] interested in non-tls traffic
* [~briang] had ideas relating to correlating client/origin connections - i.e., 
only print origin traffic related to client connection we are interested in.
* [~mlibbey] is interested in per remap enabling
* Plugin vs. Core - plugin would require restart; Apple/Comcast can’t restart 
ATS easily.  [~sudheerv] pointed out that a restart might clear condition 
trying to catch.
* Several people were interested in suggested output to pcap file - then you 
could use Wireshark's facilities to follow the connection traffic.
** [~briang] suggested to synthesize sequence numbers to facilitate this.
* Integrate [~sudheerv]'s per-ip debug feature?  Or is this unrelated?

Susan's notes:

General agreement that this is a good feature.
1. API to enable trace on a VC
2. API to process raw packet.
Agreement that should be generalized to TCP beyond.
Currently all in core.
Idea to dump to a pcap file.


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

Reply via email to