HTTP Debugging

SmashingConf Oxford talk with Curl, Ngrok and Charles Proxy as the main tools mentioned

Transcript

1. Debugging HTTP Lorna Mitchell, SmashingConf 2015
2. Why Debugging HTTP?
3. 6 Stages of Debugging
4. Denial That can't happen.
5. Frustration That doesn't happen on my machine.
6. Disbelief That shouldn't happen.
7. Testing Why does that happen?
8. Gotcha Oh, I see.
9. Relief How did that ever work?
10. Fault-Finding HTTP ... is just like fault-finding elsewhere in a web project Seeing the problem is usually harder than fixing it
11. Developer Tools Get to know the tools in your browser.
12. Developer Tools
13. Curl Curl (or cURL) is command-line multitool for HTTP http://curl.haxx.se/
14. Lornajane's Curl Cheat Sheet -X [verb] The verb to use for this request -H "[Header :value]" A header to send. Use as many times as needed -d [value] Body data as a string, a filename, or a key/value pair -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 use -b [filename] Cookies to send with the request -v to show headers for both request and response
15. Postman
16. RESTClient
17. Paw
18. Ngrok Expose local websites to the wider web https://ngrok.com/
19. Charles Proxy Multi-platform Web Debugging Proxy http://www.charlesproxy.com/
20. Debugging SSL Charles can perform a man-in-the-middle attack
21. Debugging SSL You need to authorise the "attack"
22. Make Debugging Your Super Power
23. Other Excellent Tools • Postman (Chrome) http://getpostman.com/ • RESTClient http://restclient.net/ • Paw http://luckymarmot.com/paw • Fiddler http://www.telerik.com/fiddler
24. Questions? From http://www.oreilly.com Contact: http://lornajane.net - @lornajane