Append data to the url query
daniel.haxx.se
daniel.haxx.se
But for interactive CLI usage, I always find its command line options non intuitive - take this for example, I don’t think I can really remember the difference between -d and —data-url and —url-query if I don’t use it daily. I think that the price to pay to make it backward compatible.
For that reason, I would recommend httpie as a replacement, which provides a more intuitive interface.
Here are some org-format notes I took on curl, mostly from the contents of that video: [2]
So I wonder how much demand there actually is for advanced features like this. When I need to make POST requests with queries and data, I would just use python because I most likely need to process the response (parse html, store json output to database, etc.).
Adding advanced features are nice, but IMO this might lead to over-engineering and it might be hard to maintain down the line.
curl's not exactly a new project -- this is 'down the line' for it.
I personally welcome the change. I wont use it often, but when I will, I'll be quite happy that it's there. There are a number of other features I'd give up in it's stead.
Writing a scraper for those, bash & curl comes in handy w/o needing extra cruft of file writing ceremonies (ex: with open…), just pipe straight to file.
Well, one person [1] has been maintaining it since 1998. It's a good thing that HTTP doesn't change that often.
> Easy for the client, easy for the server, easy to share, only downside that I see is that it makes things a bit obtuse for users
There are more downsides:
- processing and creating payload can be harder are you're passing plaintext w. ca. 30% size increase on average
- base64-encoded assets (e.g. SVGs) would cause a huge performance drop in WebKit (this probably has improved since the last time I ran benchmarks).
- since you're encoding content and not its location, you can't easily update the underlying resource (hence to update my version of Pong, I'd need to create a new unique URL). IIRC IPFS suffers (used to?) from a similar issue
- not an issue now, but still was 1-2 years ago: some browsers would allow only for 2 or 4kb of text in URL
> not an issue now, but still was 1-2 years ago: some browsers would allow only for 2 or 4kb of text in URL
Yes, I had in mind smaller payloads, things that would have been query params on a GET
That does raise an interesting question though. If one wanted to create a command-line tool (or, rather, toolset) as comprehensive as curl, but with a much smaller API surface, how would they go about it? Sure, some of these flags are just shorthands, and some of them could be removed entirely (-o → stdout redirection), but that still leaves a lot of options.
Perhaaps take a look at the most popular ones every now and then, but a free software project owes the world nothing.
In practice I assume (I have no practical experience) that as the project gets larger the number of involved parties grows. And suddenly you need to balance interests of not just you but also the community, contributors, large users, sponsors and possibly more.
What if I’m running curl directly without a shell (e.g. in a container). How else would I save the output to a file?
If you were starting over from scratch even trying to make it curl-like, you could probably trim down the options substantially.
The OP is in fact an example of a new option that can more-or-less cover the same functionality as some old options, plus more, but the old options remain.
This is one seriously under appreciated piece of code, and I am so grateful that it exists.
And also
$ rclone help flags . | grep "^ *--" | wc -l
665
Also, it seems some curl behaviours live in the past where only GET and POST verbs exists, ignoring others like PUT and PATCH.
Backwards compatibility is a wonderful thing, but leads to anachronisms 20 years later.
`-X` exists for anyone that doesn't want curl's divination
edit: oh no, log4j-2.11.0