Handy but incomplete
This tool is great for understanding whats going on the wire when writing and debugging an API, however it leaves me scratching my head sometimes. Frequently the app will improperly display responses that are not 200 OK. For example, a connection refused, 204 No Content, and most 400 responses all display as ((no content)), without any description, or more importantly the headers involved. I look forward to a more thorough implementation.
John90349 about
HTTP Client