On Jul 13, 2007, at 12:29 PM, Micah Cowan wrote:
sprintf(filecopy, "\"%.2047s\"", file);
This fix breaks the FTP protocol, making wget instantly stop working
with many conforming servers, but apparently start working with yours;
the RFCs are very clear that the file name argument starts right after
the string "RETR "; the very next character is part of the file name,
including if the next character is a space (or a quote). The file name
is terminated by the CR LF sequence (which implies that the
sequence CR
LF may not occcur in the filename). Therefore, if you ask for a file
"file.txt", a conforming server will attempt to find and deliver a
file
whose name begins and ends with double-quotes.
Therefore, this seems like a server problem.
I think you may well be correct. I am now unable to reproduce the
problem where the server does not recognize a filename unless I give
it quotes. In fact, as you say, the server ONLY recognizes filenames
WITHOUT quotes and quoting breaks it. I had to revert to the non-
quoted code to get proper behavior. I am very confused now. I
apologize profusely for wasting your time. How embarrassing!
I'll save this email, and if I see the behavior again, I will provide
you with the details you requested below.
Could you please provide the following:
1. The version of wget you are running (wget --version)
2. The exact command line you are using to invoke wget
3. The output of that same command line, run with --debug
--
Rich "wealthychef" Cook
925-784-3077
--
it takes many small steps to climb a mountain, but the view gets
better all the time.
