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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Wehmann wrote:
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
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
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
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
Fred Holmes [EMAIL PROTECTED] 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
