Hurl
21–30 of 33 posts
Re: Hurl
#22Very slick, but it really needs a JSON pretty printer in addition to the XML one. Most JSON services just send one huge line, which is exactly how Hurl displays it.
We do pretty print JSON: http://hurl.me/ufsmb1
Re: Hurl
#23Why no way to enter a raw POST body instead of key-value pairs? Could've been seriously useful for some web services.
Re: Hurl
#24For example I can give you this URL: http://hurl.me/ufsmb1
And you can change 'json' to 'xml' to see what changes.
Hurl was inspired by sharing curl input and output over pastebins. We should probably make this more clear.
Re: Hurl
#25A similar app, but as native OS X app (useful for localhost requests) http://ditchnet.org/httpclient/
Re: Hurl
#26It's ok, but Firebug covers this pretty well already.
Re: Hurl
#27Very, very cool.. and I love the name. That said, I regularly test APIs using actual usernames and passwords via HTTP Basic Auth. It will be a cold day in hell before I toss my credentials in cleartext into a web form. :-) I really like the syntax-highlighted, pretty-printed JSON output, though. Really handy.
Re: Hurl
#28Earlier quoted context omitted.
Yes, perhaps you are. First, watch the video: http://vimeo.com/6238577 Second, realize that this was developed from start to finish in 48 hours, by some not untalented people... they seem to have put a lot of thought into it, and the details really show. Third, saying you could do anything nontrivial in "10 lines of code" reminds me of this guy http://news.ycombinator.com/item?id=678501
First, watch the video? Doesn't that seem to emphasize the guy's point? It seems like a neat if simplistic little tool and if you have to watch a video to tell how it's something more...
Sounds like we should change this:
Hurl makes HTTP requests.
Enter a URL, set some headers, then view the response.
Perfect for APIs.
To something like this: Hurl makes HTTP requests.
Enter a URL, set some headers, get a response, then share it with others.
Perfect for demoing and debugging APIs.Re: Hurl
#29A similar app, but as native OS X app (useful for localhost requests) http://ditchnet.org/httpclient/
HTTPClient is great and was a big influence on Hurl (for instance we auto-complete headers just like HTTPClient does).
A few minutes later: everything seems to give the error:
Cannot allocate memory - fork(2)
Re: Hurl
#30Earlier quoted context omitted.
HTTPClient is great and was a big influence on Hurl (for instance we auto-complete headers just like HTTPClient does).
I can't seem to get Hurl to send application/json content. Any ideas? A few minutes later: everything seems to give the error: Cannot allocate memory - fork(2)
I'm workin' on bringing it back up.