support for --post-data argument

[Daniel Kahn Gillmor]

hey Curl folks--

wget and uclient-fetch both support the argument --post-data, which i
think is equivalent to curl's --data-raw.

LEDE/OpenWRT apparently both make use of one of these three tools (wget,
curl, uclient-fetch) interchangably). It'd be easier for those tools
that depend on one of the three if they could rely on all of them
supporting the same interface. would curl consider adding --post-data
as an alias to --data-raw?

thanks for curl,

--dkg

See also https://github.com/openwrt/packages/issues/4878

[Dan Fandrich]

Post by Daniel Kahn Gillmor
hey Curl folks--
wget and uclient-fetch both support the argument --post-data, which i
think is equivalent to curl's --data-raw.
LEDE/OpenWRT apparently both make use of one of these three tools (wget,
curl, uclient-fetch) interchangably). It'd be easier for those tools
that depend on one of the three if they could rely on all of them
supporting the same interface. would curl consider adding --post-data
as an alias to --data-raw?

IMHO, there are just too many options and too many differences between these
programs that it's pointless to try to converge them. This particular
application needs --post-data, but others use other options and there's nothing
stopping everyone else from asking for the options they need to be added as
aliases, too.

What might be interesting is a shell script, called, for example wget-curl,
that just converts (a subset of) wget options into their curl equivalents then
calls curl. Such a script would be small enough to ship with curl itself and
might be enough, if renamed to "wget", to fool a lot of programs into thinking
it's the real wget. It works for Busybox, and curl would be able to emulate a
lot more options than Busybox supports.

Post by Daniel Kahn Gillmor

Dan

-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://