Debugging HTTP
summary
A practical playbook for finding where HTTP fails: use curl with -v -H -d and a cookie jar to reproduce requests and see headers, pipe JSON through python -m json.tool, use Wireshark to capture cross-process traffic and discover a malformed access token (a PHP variable name sent instead of the hex) that causes 400/500s, then fix code and verify a 201 created. Use Charles proxy ($50) to rewrite hosts, route a phone through the laptop, throttle networks and install its CA to inspect HTTPS.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:15Debugging
- 3:24Curl
- 7:45Command Line Tool
- 12:42Create data using Curl
- 18:07Python JSON library
- 18:27Wireshark
- 26:35Charles Proxy
- 30:56Charles Proxy Tricks
- 31:16Sunshine PHP
- 33:35Charles Rewrite
- 34:54Firefox Rewrite
- 37:05Charles Network Proxy
- 40:18Rewrite Rules
- 41:03Test Data
- 42:45SSL
- 44:40HTTP tools
- 46:48Debugging attitude
- 48:15Best tool
- 48:58Wrap up
related talks
37mLeverage Network Debugging to Elevate Your Apps' Performance Quality
43mHTTP Can Do That?!
01h 01mDebugging Your Website with Fiddler and Chrome Developer Tools
01h 14mhttp://exploration
27mSaimon Sharif - We'll do it live: Underhanded Debugging Tactics
01h 00mDebugging your website with Fiddler and Chrome Developer tools
27mReverse Engineering a Web API
28mMy Favourite Errors