On 07/13/2018 07:08 AM, bruce wrote:
Hi.
Trying to wrap my head around what I need to setup on a test system to
be able to capture/view (in a file or via app output) the https
traffic. My use case I have a test app talking to a remote server on
"https" and I want to be able to see what the traffic flow is in terms
of get/post cmds...
I see different sites/articles on the need to setup a proxy
server/certs and to then install/insert the cert in the "browser"
location. In my case I'm using a test headless browser, so I'm trying
to get a basic model of how this can work.
So, if anyone has insight/pointers feel free to share!!
If the browser is Linux-based, use tcpdump to capture all of the traffic
between the browser and server and save it to a file. Run this in a
separate CLI window on the browser machine as root:
tcpdump -i any -vvv -w <save-file> host <name-of-server>
Once you've captured all the traffic, copy <save-file> to a machine
with a GUI and use wireshark-gtk to analyze the file:
wireshark-gtk -r <save-file>
Pretty standard fare.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Programmers often confuse Halloween and Christmas. -
- After all, 31 Oct is the same as 25 Dec! -
----------------------------------------------------------------------