xh

xh has sessions. https://github.com/ducaale/xh

httpie (xh) gives way better UX for api testing and related tasks. https://github.com/httpie/cli https://github.com/ducaale/xh

I use httpie (not httpie actually, https://github.com/ducaale/xh but it has the exact same ux). For the life of me, I can't remember curl flags for some reason. Even fucking -X POST... Sending JSON is pain too. For quick and easy http requests, httpie has been fantastic.

I can understand why people would find `ut` convenient. That said, I would caution against trying to include too much functionality. What is too much? I don't have a clear idea on this yet. But I would probably argue that including HTTP functionality is going too far. Why? Because there are already amazing tools dedicated to this already. On the client side, see `xh` [1]. On the server side, see `miniserve` [2]. Both have approximately 7K stars on GitHub. It seems wiser to let specialized projects focus on a particular functional area; this is better for users and less work for maintainers. [1]: https://github.com/ducaale/xh [2]: https://github.com/svenstaro/miniserve

In https://github.com/ducaale/xh it's something like xh POST api.github.com/repos/owner/repo/issues \ Authorization:'Bearer ghp_token123' \ Accept:application/vnd.github.v3+json \ title='Bug Report' \ body='Something is broken' \ labels:='["bug","priority-high"]' \ assignees:='["developer1","developer2"]'

xh is Nice: https://github.com/ducaale/xh There's also curlie: https://github.com/rs/curlie

https://github.com/ducaale/xh is where it's at, haven't used curl in years.

Is this what you're referring to? https://github.com/ducaale/xh Seems like maybe it's written in rust? Still looks slick!

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.

Check out xh - much easier to use than curl and faster than HTTPie. https://github.com/ducaale/xh

HTTPie (the CLI version) 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. Although I might give this Desktop version a try for more complex APIs. 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

https://github.com/usebruno/bruno, https://github.com/hoppscotch/hoppscotch, https://github.com/flawiddsouza/Restfox If you want a more minimal solution/CLI https://github.com/httpie/cli and https://github.com/ducaale/xh work

Couple more things wget can do that curl can't. 1. wget can resolve onion links. curl can't(yet). You'll get a curl: (6) Not resolving .onion address (RFC 7686) 2. curl has problems parsing unicode characters curl -s -A "Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0" https://old.reddit.com/r/GonewildAudible/comments/wznkop/f4m_mi_coño_esta_mojada_s… will give you a {"message": "Bad Request", "error": 400} wget on the other hand, automatically converts the ñ to UTF-8 hex - %C3%B1 - 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