Plus 1 for for Charles. In the last month I've used it to determine:
- What an OAuth-signed SOAP envelope looks like, when Google (who prefer OAuth and require SOAP for some APIs) don't yet have it documented.
- That Chrome will encode links itself if necessary, but Firefox will not, causing a download on a colleagues app to not work on FF.
- That I'd accidentally seyup up my non-desktop app as a desktop app when registering for access to the Twitter API, resulting in an XML error response that Chrome wasn't showing me.
All over HTTPS. If you don't have an app like this (works on Windows, Mac and Linux) you need it.
- What an OAuth-signed SOAP envelope looks like, when Google (who prefer OAuth and require SOAP for some APIs) don't yet have it documented.
- That Chrome will encode links itself if necessary, but Firefox will not, causing a download on a colleagues app to not work on FF.
- That I'd accidentally seyup up my non-desktop app as a desktop app when registering for access to the Twitter API, resulting in an XML error response that Chrome wasn't showing me.
All over HTTPS. If you don't have an app like this (works on Windows, Mac and Linux) you need it.