please don't add these. I don't think we would like to add a new pair
of --FOO-data, --FOO-file for any method we will implement. As already
suggested by Hrvoje, just add --body-data and --body-file that are
synonyms for --post-data and --post-file; we can't drop these for
backward
Darshit Shah dar...@gmail.com writes:
please don't add these. I don't think we would like to add a new
pair
of --FOO-data, --FOO-file for any method we will implement. As
already
suggested by Hrvoje, just add --body-data and --body-file that are
synonyms for
Darshit Shah dar...@gmail.com writes:
Reusing post-data and post-file is not intuitive enough when we support
more options through --method.
Say, someone wished to use --method=PUT. In that case using --post-data
or --post-file is counter intuitive. Hence the need to unify them
Also, alongwith implementing --body-data and --body-file should I mark the
--post-data and --post-file commands as deprecated? Or is there a different
protocol to follow before marking a command as deprecated?
On Mon, Mar 11, 2013 at 7:38 PM, Darshit Shah dar...@gmail.com wrote:
None.
Fine,
Darshit Shah dar...@gmail.com writes:
Also, alongwith implementing --body-data and --body-file should I mark
the --post-data and --post-file commands as deprecated? Or is there a
different protocol to follow before marking a command as deprecated?
I don't see any real value to mark
I was just glancing through wget’s FAQ today and noticed something odd
in the last entry,
http://wget.addictivecode.org/FrequentlyAskedQuestions#Is_there_a_way_to_hide_my_clear-text_user.2BAC8-pass_combo_from_the_process_table.3F
. It suggests that using the following will hide the password from
Thanks for your your patch! Some comments:
Darshit Shah dar...@gmail.com writes:
Attaching a patch to make wget abort instead of sending an empty request if
the file pointed to in --post-file does not exist.
+ return FILEBADFILE;
what exit status will be returned by the wget
