Random plug: Another invaluable tool for API analysis is http://mitmproxy.org.
Thanks for mentioning it! :)
One of the authors here, happy to answer any questions.
Wow, this looks extremely interesting, I'll definitely keep this in mind!
Re:Curl vs. Wget
by mschuster91 on Thursday March 03, 2016 @03:07AM
(#11215601)
Use the Chrome Postman extension together with Postman Interceptor. It's really awesome.
I'd just like to mention HttpRequester here, which is a very similar FLOSS addon for Firefox.
Re:Curl vs. Wget
by jsingleton on Thursday March 03, 2016 @05:30AM
(#11216024)
Yes, wget is fantastic for mirroring www and ftp sites and I use it a lot for that purpose. It's magic [0]. I hadn't realized that it didn't support compression though, which might explain why it's so slow in some cases. Not normally a problem as it just runs in the background on a schedule.
Curl supports gzip and deflate. It would be great if support for sdch and br were added too. Brotli is in Firefox 44 and can be enabled in Chrome Canary with a flag. SDCH has been in Chrome for a while and is used on Google servers.
Re:Curl vs. Wget
by stephengillie on Thursday March 03, 2016 @05:43AM
(#11216060)
The Win64 latest version of curl doesn't seem to support gzip nor deflate. I have to remove those options when copying from Chrome developer tools and pasting into a script. I'd report a bug but their page doesn't seem to have an obvious link.
Github? https://github.com/curl/curl
Totally agree. I love curl for testing API request/responses manually. It's usually a huge part of navigating my way around a new API that doesn't have a client library available for whatever language I'm using at that time.
I also use it for weird requests that need special headers or authentication.
Wget is the first thing I turn to when I'm downloading anything remote from the command line or scraping some remote content for analysis.