SmashingConf Oxford talk with Curl, Ngrok and Charles Proxy as the main tools mentioned
Lorna Mitchell, SmashingConf 2015
Why Debugging HTTP?
6 Stages of Debugging
That can't happen.
That doesn't happen on my machine.
That shouldn't happen.
Why does that happen?
Oh, I see.
How did that ever work?
... is just like fault-finding elsewhere in a web project
Seeing the problem is usually harder than fixing it
Get to know the tools in your browser.
Curl (or cURL) is command-line multitool for HTTP
Lornajane's Curl Cheat Sheet
-X [verb] The verb to use for this request
A header to send. Use as many times as needed
-d [value] Body data as a string, a filename, or a key/value
-s The "silent" switch, to hide curl's progress meter
when piping the output to something else
-c [filename] Where to store any incoming cookies for future
-b [filename] Cookies to send with the request
-v to show headers for both request and response
Expose local websites to the wider web
Multi-platform Web Debugging Proxy
Charles can perform a man-in-the-middle attack
You need to authorise the "attack"
Make Debugging Your Super Power
Other Excellent Tools
• Postman (Chrome) http://getpostman.com/
• RESTClient http://restclient.net/
• Paw http://luckymarmot.com/paw
• Fiddler http://www.telerik.com/fiddler
Contact: http://lornajane.net - @lornajane