Michelle Konzack napsal(a):
Am 2008-09-20 22:05:35, schrieb Micah Cowan:
I'm confused. If you can successfully download the files from
HOSTINGPROVIDER in the first place, then why would a difference exist?
And if you can't, then this wouldn't be an effective way to find out.
I mean, IF you
Am 2008-09-20 22:05:35, schrieb Micah Cowan:
I'm confused. If you can successfully download the files from
HOSTINGPROVIDER in the first place, then why would a difference exist?
And if you can't, then this wouldn't be an effective way to find out.
I mean, IF you have a local (master) mirror
Hi Micah,
Your're right - this was raised before and in fact it was a feature Mauro
Tortonesi intended to be implemented for the 1.12 release, but it seems to have
been forgotten somewhere along the line. I wrote to the list in 2006 describing
what I consider a compelling reason to support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David wrote:
Hi Micah,
Your're right - this was raised before and in fact it was a feature
Mauro Tortonesi intended to be implemented for the 1.12 release, but it
seems to have been forgotten somewhere along the line. I wrote to the
list in
Hello Micah,
Am 2008-09-02 15:49:15, schrieb Micah Cowan:
I think I'd need some convincing on this, as well as a clear definition
of what the scope for such a feature ought to be. Unlike curl, which
groks urls, Wget W(eb)-gets, and file:// can't really be argued to
be part of the web.
Right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michelle Konzack wrote:
Imagine you have a local mirror of your website and you want to know why
the site @HOSTINGPROVIDER has some files more or such.
You can spider the website @HOSTINGPROVIDER recursiv in a local tmp1
directory and then,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Petri Koistinen wrote:
Hi,
I would be nice if wget would also support file://.
Feel free to file an issue for this (I'll mark it Needs Discussion and
set at low priority). I'd thought there was already an issue for this,
but can't find it (either
