Well, it's not simply the %20 that is the problem. Here's a simple, straightforward
URL that has %20's in it and it downloads just fine. My apologies for the bum steer.
Fred Holmes
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\fh
Here is an example of an instance where a filename containing
%20 fails, but replacing the %20 with spaces, and enclosing in
quotes works. At the end I find that just putting the original
URL (with %20) in quotation marks makes it work. There is
something else unusual about this URL.
The first
At 04:55 AM 5/21/2004, Hrvoje Niksic wrote:
>OTOH, if you're talking about *file* names, %20 should already be
>converted to space.
Yes, these URLs are for files, e.g., .pdf and .doc and .zip files. When I get to work
today, if I can make a few minutes of time, I'll post an explicit example (or
But I want WGET to convert %20 to space (I think). I'm using 1.9.1. I haven't
checked to see if there is a new stable version. I'm using the windows binary. I'd
love to go linux, but the startup transient is too much. (And the computer they
furnish me at work is Windows)
I regularly use WGE
Fred Holmes <[EMAIL PROTECTED]> writes:
> But I want WGET to convert %20 to space (I think).
Why would you want that? A URL with a literal space is illegal, at
least for HTTP -- Wget would have to convert the space to %20 to be
able to send the URL to the HTTP server anyway.
OTOH, if you're tal