Darshit Shah <dar...@gmail.com> writes: > this change will break backward compatibility, we need a new option for > that and leave the default unchanged. > > I am not suggesting that we change the working of --post-file and --post-data > commands. Unlike the patch I just submitted, we could could de-couple the > --post-file, > --post-data method and the --body-file --body-data methods, so that the older > --post-file/data methods work in exactly the same way, but only the NEW > --body- methods > change.
I don't think this is a good idea. It will create confusion, I prefer them to work exactly in the same way so one day we can drop the --post-* commands. > How do you expect the file to be in this case? Will wget do any > filtering? > > The file should be read in binary mode and sent as-is. However, I am > unsure if wget should do any filtering of filetypes. I was more thinking of how to specify "boundary" for instance. Expect that the file is well formed doesn't seem nice to users. >At most, we could prevent the file from being an executable >binary. (ELF in Linux, Win32 EXE in Windows, etc.) Why? -- Giuseppe
