Fred Holmes <fsh <at> cpcug.org> writes: > > If I have a URL that has %20 in place of spaces, and I use the URL directly as the argument of WGET, it seems that > the file is always "not found". I've discovered that if I replace each %20 with a space, and put quotation > marks around the entire URL, it works. > . . .
This topic is of interest to me, since I am using wget in a Windows XP command shell, to fetch files from a HTTP server. A number of the file names have spaces in them and in the url these were replace by "%20"; these files did not successfully download. What I realized is that the "%" character is not protected by using double quotes surrounding the url. I could see this by having "echo on" as the first line of my command file. The "escape" character "^" that protects other special characters in the command shell doesn't help in the case of "%". What does seem to work is to replace "%20" by "%%20". I am not a subscriber to wget@sunsite.dk so please include my email address in replies.
