Sniffing the Wire - HTTP Debugging the easy and hard way
If you work in web services for any length of time, eventually you'll need to sniff the packets that are flowing and figure out what [insert framework of choice] is doing to your precious data.
Fear not, there is an easy way. For the sadists, there is also a hard way.
Read on, I'll show you both.
YATT is amazing. It's everything you need, nothing you don't. Its just for HTTP, which is great. It has url filters, which is great. Its fast, thin, and STUPID simple. Great.
Download it. I'd get a newer version of WinPCap, especially if you're on a 64bit box or Windows 7.
How To Use:
- Skip this section, it literally has 4 options.
- Still here, fine. File->Start Trace
- Select WinPCap Capture
- Select your IP/Interface
- Type in a filter: www.example.com -or- leave it blank
- select what port you're talking on (Hint: 80)
The Hard Way
Use this if:
- If you're on a remote headless Unix/Linux system
- You don't want to install windows
- You cant get Wireshark to run natively, but have it installed somewhere else
- On the system your send/receiving packets, run this as root:
$ tcpdump -s 65535 -w /someplace/tcpdump.out - Now, make some traffic.
- Control-C tcpdump.
- Copy the file to the box that has wireshark on it.
- In wireshark, File->Open tcpdump.out
Trackbacks
Trackback specific URI for this entry
No Trackbacks