Charles Kozierok <charles...@gmail.com> writes: > But I guess the bigger question is why a Windows version of wget > wouldn't gracefully handle removal of the standard end-of-line > characters. I'm not even sure I can figure out how to properly write > the data out to the file without the 0A0D at the end.
As an user I expect that wget doesn't modify the data. Imaging wget removes trailing "\r\n" sequences, how to create a file in a way that "\r\n" is appended at the POST payload after the file content? I think it is easier to use a sane editor (or an hex editor) that gives you full control on your data. Cheers, Giuseppe
