Hmm - changing the rename schema would potentially create a HUGE issue with
clobbering.
For example, and quite hypothetical...
Given a directory with the following:
index.html
index-1.html
index.1.html
All three are served by the server and rendered by the browser. They are
distinct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher G. Lewis wrote:
Hmm - changing the rename schema would potentially create a HUGE issue with
clobbering.
For example, and quite hypothetical...
Given a directory with the following:
index.html
index-1.html
index.1.html
Hrvoje Niksic wrote:
It just occurred to me that this change breaks backward compatibility.
It will break scripts that try to clean up after Wget or that in any
way depend on the current naming scheme
I'm also a bit hesitant about changing the way files get named.
With a .1 at the absolute
Hello,
I use wget to retrieve an XML feed. The problem is that sometimes I get timeout
error. I used the good wget options to handle this problem, but when wget
retries to download the file again, the data are appended to the file which
causes a bad file. Here is wget command line:
wget -c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
moisi wrote:
Hello,
I use wget to retrieve an XML feed. The problem is that sometimes I
get timeout error. I used the good wget options to handle this
problem, but when wget retries to download the file again, the data
are appended to the
Andreas Pettersson [EMAIL PROTECTED] writes:
And how is .tar.gz renamed? .tar-1.gz?
Ouch.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
I admittedly do not know much about web server responses, and I
have a question about why wget did not retrieve a document. . . .
I executed the following wget command:
wget --recursive --level=20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
Thanks. I unzipped those binaries, but I still have a problem. . . .
I changed the wget command to:
wget --recursive --level=20 --append-output=wget_log.txt -econtent_dispositi
on=on
