-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hrvoje Niksic wrote: > A friend pointed out that Wget doesn't allow adding a request body to > GET requests, since both --post-data and --post-file automatically > switch to POST. It would be nice to support the equivalent of curl's > --request option, which specifies a custom request method for HTTP.
Personally, I'm not particularly keen on implementing or maintaining such a thing. I don't really see it as falling under Wget's general scope, which as I see it is to non-interactively fetch content that a user might consider as "web content", in a matter comparable to that used by typical interactive clients (mainly web browsers and ftp clients). Isn't that why we haven't provided support for even official HTTP methods such as OPTIONS, TRACE, PUT and DELETE? Curl, on the other hand, isn't intended so much for fetching specifically, as it is for "doing URLs", whatever that may entail, and transferring data to a server is as important a goal for that project as fetching data from one. OTOH, if we do wind up at some point with a next-gen Wget that wraps libcurl for its actual protocol-level work (an idea I still play with), then it might be enough of a "low-hanging fruit" to support it. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. Maintainer of GNU Wget and GNU Teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpKWEAACgkQ7M8hyUobTrFicwCdEXItXNLkEAMLvlGMrinPx9Gz SCYAniStxlaFQpfNGil2iqVeKV6H0Y7c =ctJR -----END PGP SIGNATURE-----
