> this change will break backward compatibility, we need a new option for > that and leave the default unchanged. >
Why will it break backward compatibility? The --method option has just been pushed, not released as yet. As long as we implement this before the next release of Wget, I don't see why we may not edit that code. 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. > 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. At most, we could prevent the file from being an executable binary. (ELF in Linux, Win32 EXE in Windows, etc.) -- Thanking You, Darshit Shah Research Lead, Code Innovation Kill Code Phobia. B.E.(Hons.) Mechanical Engineering, '14. BITS-Pilani
