REST worst practices

Re:REST worst practices by phillco on Friday January 20, 2012 @06:13PM (#3491680)

What I like about using GET (and, to some extent, POST) is that it makes it trivial to test your API in a browser while developing it. Just paste in the URL and you get the raw response, fetch time analysis, and everything else the Chrome developer tools provide you.

This shouldn't matter much, but it does.

[ Parent | on HN ]

Re:REST worst practices by FuzzyDunlop on Friday January 20, 2012 @07:07PM (#3491913)

XHR Poster[0] sounds like an extension you'll enjoy. It provides a much more comprehensive testing interface.

[0]http://goo.gl/UFSdZ (links to Chrome extension store)

[ Parent | on HN ]

Re:REST worst practices by symkat on Saturday January 21, 2012 @01:01AM (#3492758)

I'd add that one of the best features of XHR Poster is that it uses your cookies and any authentication you've already performed in Chrome when sending the requests.

I had to build an API that lived inside a system with entirely too many authentication/cookie checks and using curl was becoming too awkward for testing, this saved me a lot of time.

[ Parent | on HN ]

Re:REST worst practices by ajtaylor on Saturday January 21, 2012 @02:11AM (#3492873)

Thank you so much for the pointer! I've installed it, and I imagine I'll be using it quite a bit in the coming weeks at $work.

[ Parent | on HN ]