REST Client for Google Chrome
chrome.google.com
chrome.google.com
You can also export these collections and share them with other team members.
This is particularly useful for sanity checking before deploys e.g. just running through each API call to make sure users can login and perform primary actions.
I'd be really interested to hear more about why the dependency is there and what the interplay between the two extensions and the cloud bit of the service is?
It is worth mentioning though that the link points to a hosted app - not an extension. You do require an extension for this to work but it is very lightweight and rather simple. The extension only provides the ability to send HTTP requests as you see them.
Websecurify looks interesting in itself but requires "access to your data on all websites" permission which means doing a load of research into what it's actually doing etc etc which seems like a lot of effort just to try out a rest client.
Best of luck to them though, Postman made by workflow testing API's hugely more efficient so if they manage to improve on that it'll be a great tool.
I mean, if I have to fill a full request myself, I'd better directly use a terminal.
Right now, POSTMAN fills all my needs, and the alternative will have to be really good to make me change.
Maybe people not aware of postman would appreciate more.
One of the main uses of a rest client in a chrome extension (e.g. postman/advanced REST client) is so you can use it offline. The entire functionality of the webpage is written in JS (https://suite.websecurify.com/rest/script) so it could be easily packaged into a true chrome extension, frankly as it stands this seems to be a bit of a half arsed attempt to get more exposure.
Also, there are no notifications when updating extensions anyway - not that you can prevent those updates or even bother reading the code. Nothing changes really from the perspective of the browser security model.
Seems that both solve the same problem.
When you work in a team with non-developer testers they tend to use a GUI REST client like this, while most of the developers will prefer working with curl commands instead.
You don't want to know how many hours have been wasted manually converting these calls back and forth ... especially when somebody converts them incorrectly.
Soon, it will be possible to go the other way around as well, i.e. convert a request to curl.
I hope this will be helpful to you in the future.
Like the others have mentioned here, there are a couple of tools in chrome that try to solve the same problem. Not that it is a bad thing. Has anyone used them all to summarize pros / cons ?
[1] https://chrome.google.com/webstore/detail/advanced-rest-clie...
A web browser is literally a "dedicated REST client". REST is just HTTP. It's the pattern HTTP to exchange messages. Representations and methods. Sure, HTML forms never implemented the full range of methods [facepalm], but most engines allow method parameter overrides (_method=PUT|DELETE). And it does get harder when doing these live via JavaScript, and exchanging data other than HTML like JSON.
Of course I use HTTP tools other than the generic web browser UI. Firefox extensions get you pretty far with HTTP logging/modification like Firebug, Poster, TamperData. There's also some standalone apps like Fiddler and friends. But meh.
GET XUsername:ADMIN https://localhost:443/resources/myresource/1 HTTP/1.1 Host: target
gives an error in the REST: "Your request contains errors"