11–20 of 24 posts
Holy crap, yes please! I literally need an interactive HTTP client like this RIGHT NOW. Thanks! I've been dealing with a really hairy, picky quasi-RESTful API in Objective C, and it can be extremely hard to differentiate between a bug in my code and a bug in the API at times. Having an interactive console like this is going to save me a huge amount of time and hassle. Thank you so much for writing this!
Holy crap, yes please! I literally need an interactive HTTP client like this RIGHT NOW. Thanks! I've been dealing with a really hairy, picky quasi-RESTful API in Objective C, and it can be extremely hard to differentiate between a bug in my code and a bug in the API at times. Having an interactive console like this is going to save me a huge amount of time and hassle. Thank you so much for writing this!
What about telnet? (I did not downvote you, BTW.)
is this something one would use to play with API requests?
Earlier quoted context omitted.
What about telnet? (I did not downvote you, BTW.)
general ease of use, including highlighting, simple management of GET/POST/PUT/DELETE, cookies, etc.
sounds like a solution looking for a problem.
um yeah - what's wrong with plan ole http? curl has never come up short.
In the near future, the difference will be more striking. The ability to parse and build requests on various media types will make htty even better at the tasks of both API exploration and HTML screen-scraping.
Holy crap, yes please! I literally need an interactive HTTP client like this RIGHT NOW. Thanks! I've been dealing with a really hairy, picky quasi-RESTful API in Objective C, and it can be extremely hard to differentiate between a bug in my code and a bug in the API at times. Having an interactive console like this is going to save me a huge amount of time and hassle. Thank you so much for writing this!
What about telnet? (I did not downvote you, BTW.)
> Response codes between 500 and 599 appear flashing black on yellow to indicate a server error
Note that flashing stuff is one of the major sins of UI design, on websites as well as console applications. Even on really serious errors, flashing text is just distracting and makes the oh so important information hard to read.
I strongly recommend to remove the blinking.
Instead, you could rethink the color scheme. However, the current colors are working quite well for me, so I guess that simply removing the flashing will already do the trick.
Holy crap, yes please! I literally need an interactive HTTP client like this RIGHT NOW. Thanks! I've been dealing with a really hairy, picky quasi-RESTful API in Objective C, and it can be extremely hard to differentiate between a bug in my code and a bug in the API at times. Having an interactive console like this is going to save me a huge amount of time and hassle. Thank you so much for writing this!
1) If I hit Ctrl-D - it says "* Type qui[t] to quit."
If you know what I want to do, DO IT.. don't argue with me. Why would you write special extra code that specifically recognizes what the user wants to do and then tell them to do it another way?
2) putting a character in [X] usually means X is the character to hit. The help text is difficult to parse compared to what's normal....
Oh - I like the tool BTW - very handy otherwise.....