prestige VS ht

I've not used it, but have heard of Prestige (https://github.com/sharat87/prestige). It bills itself as "A text-based HTTP client in the browser. An interface-less Postman." I hope that helps!

9. prestige

Shameless plug: There's also Prestige at https://prestigemad.com, which is very similar but works right in the browser. You can save your files as Gists as well. Templating with variables is also supported with `${}` syntax, like Javascript's template strings.

But gRPC support is not built yet. It's on the roadmap.

There's also https://prestigemad.com, a text based API testing tool, like Postman. I'm the developer behind it and is open source at https://github.com/sharat87/prestige.

Login not required!

Hey! I did the same thing, rewrite httpbin in Go, and put it up on https://httpbun.com. I did it because I needed a fast endpoint like httpbin, with a few extras, and with working redirect endpoints. I needed this for testing Prestige. (Sorry for inserting a shameless plug in here, but httpbun and httphub are just so close to each other I couldn't shut up 🙈).

Still early days at https://prestigemad.com (recently discussed at https://news.ycombinator.com/item?id=27412445)

- Backend is a Django project, database is PostgreSQL.

- Frontend powered by Mithril.js and the editor by CodeMirror.

- Hosted on a $5 box on EC2.

- GoatCounter for analytics.

- CloudFlare for DNS, NameCheap for domain.

Also https://httpbun.com

- Backend is a vanilla Go project.

- Frontend is plain HTML and CSS, I don't recall it having any JS at all.

- Hosted on the same $5 box on EC2.

- No analytics (yet).

- CloudFlare for DNS, NameCheap for domain.

It is refreshing to see how much I can squeeze out of a $5 box. I don't intend to stay with EC2 for long, but when its cheap, I'd rather spend my time improving Prestige.

No need to use curl, make HTTP requests great again with https://github.com/ducaale/xh

Except when you actually enjoy things being fast. For example, HTTPie easily adds 0.5-1s delay to every request because it's written in Python, especially on the first invocation. xh (https://github.com/ducaale/xh), on the other hand, starts immediately because it's written in Rust. I very much like this trend.

HTTPie is great and was a big improvement for me over cURL.

However, I ended up switching to xh[1] as it's significantly faster and I prefer its output.

https://github.com/ducaale/xh

No, but unless portability is a concern or you're massively familiar with curl, you might want to consider xh. It's much more intuitive.

https://github.com/ducaale/xh

xh

wget on the other hand, automatically converts the ñ to UTF-8 hex and resolves the link perfectly.

I've searched the curl manpage and couldn't find a way to solve this. Please help.

I'm having to use `xh --curl` [1] to "fix" the links before I pass them to curl.

[1] https://github.com/ducaale/xh

Very nice, you should add xh to the User-Agents though.

While not a rewrite - one recent tool for making http requests which i quite enjoy is:

https://github.com/ducaale/xh

It's basically python httpie rewritten in rust. my only gripe is that i keep forgetting that it exists - and that "xh" is for http and "xhs" is for https.

So i frequently end up with curl anyway:)