Re:Make HTTP requests from your browser
by johns on Sunday January 08, 2012 @02:48PM
(#3440327)
Hurl.it was originally created by Chris Wanstranth and Leah Culver at the 2009 Rails Rumble. We (Twilio) just took over maintenance of the project because it has some obvious utility when testing URL callbacks and webhooks. We want to make some improvements to it, so if you have any ideas or suggestions, I'd love to hear them. You can post them here or create an issue on the current home of the project on Github: https://github.com/twilio/hurl
Re:Make HTTP requests from your browser
by bgruber on Sunday January 08, 2012 @06:53PM
(#3440926)
For chrome, I like using the "REST Console" extension (https://chrome.google.com/webstore/detail/cokgbflfommojglbmb...), which I believe has all of the benefits you listed. The "credentials stored in a browser" thing is the main reason for me to be using it.
What I want to say is that services like this have a security flaw by design which allows random people to execute strange statements in the name of Hurl.
There are certainly other ways to execute malicious HTTP requests (for example, let the Google Bot do it), but still, it should be pointed out.
Re:Make HTTP requests from your browser
by WA on Sunday January 08, 2012 @03:05PM
(#3440369)
Yes, not Hurl itself. But Hurl can be used to execute malicious statements.
It is a difference, whether an attacker uses his own IP address (or a setup with various VPNs and proxies) or uses Hurl for it so that the target website sees only Hurl's IP in its logs.
In times of free WiFi, the traceability of malicious requests is definitely reduced anyway, but Hurl could potentially add another layer that can be used by an attacker to obscure his/her origin. I'm not saying that this is a major security issue, it is just a flaw by design, which I wanted to point out.
Re:Make HTTP requests from your browser
by taf2 on Sunday January 08, 2012 @11:37AM
(#3439861)
Very useful - to send a curl to someone - to explain why a response is incorrect or provide context about a service response... Sure you could use curl + gist - but there is something I nicer here - for example on my iPhone I could use hurl.it to explain a bad response via email without having to drop into a shell... Great service thanks!
Re:Make HTTP requests from your browser
by johns on Sunday January 08, 2012 @02:39PM
(#3440308)
No need to pay, we (Twilio) are now actively maintaining it and going to be adding some new features. Common templates exists (not documented) yet. You can put values in URL parameters and the fields will autopopulate effectively giving you URL-based templates. Responses are already saved, click the permalink to get back to them later.
If you have any other feedback items, feel free to post them here or on https://github.com/twilio/hurl and we'll take a look at them. Pull requests are even better.
Re:Make HTTP requests from your browser
by suresk on Sunday January 08, 2012 @02:44PM
(#3440316)
If you're on OS X, I sell one for $2 on the Mac App Store - http://www.uresk.net/httpclient/. I'm working on a major update, and I'd be interested in hearing some more details about the features that would make a tool like this useful to you.
If you (or anyone else on HN) want to check it out but don't want to shell out a few bucks for it, send me an email (<my username>@gmail.com) and I'll get you a coupon code for a free copy.
Re:Make HTTP requests from your browser
by raesene2 on Sunday January 08, 2012 @12:27PM
(#3439989)
Interesting idea, could be very useful. One thing with this kind of service is always how they handle validation of data from the 3rd party service (eg, in headers). So as an example http://hurl.it/hurls/db870b49c7203ec9acb47ba7769c126146b1768... executes javascript in the context of their site... (just a pop-up box with hi, but could be any script..)
Re:Make HTTP requests from your browser
by obeattie on Monday January 09, 2012 @05:31AM
(#3442030)
I've used this extensively before; brilliant little service, but I've recently started using the "REST Console" Chrome extension, which is bloody brilliant:
Re:Make HTTP requests from your browser
by godDLL on Sunday January 08, 2012 @01:03PM
(#3440086)
Do you have some limits in place, or can I just expect it to proxy all of my web traffic when I want it to (which I can do with one JS statement right on this page)? Magic WebKit Inspector is going to ruin your hosting bill.
Re:Make HTTP requests from your browser
by mtrimpe on Sunday January 08, 2012 @12:59PM
(#3440073)
Minor bug-report: when you keep clicking on the 'Send' button continuously it will occasionally show the JSON response in-browser instead of updating the UI.
And no, I'm not crazy. I was trying to test GitHub's rate-limiting. ;)
And you can follow @hurlit for updates
* Better security for the user (the paranoid in me do not want to send my credentials through a third party site).
* It could use the credentials stored in the browser (cookies, basic-auth, etc).
* The IP of the requester would not be hidden, allowing IP filtering for development servers.
* It could run on a PC that is not connected to internet.
[0] http://wiki.developer.myspace.com/index.php?title=OAuth_Test... [1] http://googlecodesamples.com/oauth_playground/ [2] https://code.google.com/oauthplayground/
Ironically, this is exactly what the browser is for.
What I want to say is that services like this have a security flaw by design which allows random people to execute strange statements in the name of Hurl.
There are certainly other ways to execute malicious HTTP requests (for example, let the Google Bot do it), but still, it should be pointed out.
Hoping that an attacker can't use curl probably isn't a good security solution...
It is a difference, whether an attacker uses his own IP address (or a setup with various VPNs and proxies) or uses Hurl for it so that the target website sees only Hurl's IP in its logs.
In times of free WiFi, the traceability of malicious requests is definitely reduced anyway, but Hurl could potentially add another layer that can be used by an attacker to obscure his/her origin. I'm not saying that this is a major security issue, it is just a flaw by design, which I wanted to point out.
If an attacker is relying on using Hurl as their only source of anonymity they're not very competent.
http://checkip.dyndns.com/ -> http://hurl.it/hurls/6fb24ac23d7c64a7edbcfceecd77c3d02586416...
127.0.0.1 -> http://hurl.it/hurls/7ad9448295a320acfe11160f0a8986fa591329f...
https://github.com/defunkt/hurl
It's a pretty thin proxy.
It's been an absolutely indispensable tools for debugging (crazy) API's while developing https://zapier.com.
If you have any other feedback items, feel free to post them here or on https://github.com/twilio/hurl and we'll take a look at them. Pull requests are even better.
[1]: http://www.charlesproxy.com/
[1]http://www.parosproxy.org/download.shtml
If you (or anyone else on HN) want to check it out but don't want to shell out a few bucks for it, send me an email (<my username>@gmail.com) and I'll get you a coupon code for a free copy.
http://www.fiddler2.com/fiddler2/
A hurl.it along those lines would be very useful.
I couldn't live without it.
[1] http://goo.gl/UFSdZ
http://www.rexswain.com/httpview.html
Since October 1999, actually.
https://github.com/twilio/hurl/pull/9
https://chrome.google.com/webstore/detail/cokgbflfommojglbmb...
Particularly http://httpong.com/response but the other parts can show you what hurl.it is sending.
And no, I'm not crazy. I was trying to test GitHub's rate-limiting. ;)