If we were going to leave this behavior in for some time, then I think
it'd be appropriate to at least mention it (maybe I'll just mention it
anyway, without a comprehensive explanation
It would probably be sufficient to just add a very brief mention
to the docs of 1.11, the two things tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Pattist wrote:
>>
>> > When deciding whether it should delete a file afterwards, however, it
>> > uses the _local_ filename (relevant code also in recur.c, near "Either
>> > --delete-after was specified,"). I'm not positive, but this probably
>> >
> When deciding whether it should delete a file afterwards, however, it
> uses the _local_ filename (relevant code also in recur.c, near "Either
> --delete-after was specified,"). I'm not positive, but this probably
> means query strings _do_ matter in that case. :p
>
> Confused? Coz I sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> As I currently understand it from the code, at least for Wget 1.11,
> matching is against the _URL_'s filename portion (and only that portion:
> no query strings, no directories) when deciding whether it should
> download something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Pattist wrote:
> Micah Cowan wrote:
>> Well, -E is special, true. But in general the second quote is (by
>> definition) correct.
>>
>> - -E, obviously, _shouldn't_ be special...
>
> I hope it's clear I'm not complaining.
I didn't take it as comp
Micah Cowan wrote:
Well, -E is special, true. But in general the second quote is (by
definition) correct.
- -E, obviously, _shouldn't_ be special...
I hope it's clear I'm not complaining. Wget is great and your efforts
are very much appreciated. I just wanted to document the behavior I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Pattist wrote:
> Micah Cowan wrote:
>> After another look at the relevant portions of the source code, it looks
>> like accept/reject rules are _always_ applied against the local
>> filename, contrary to what I'd been thinking. This needs to be ch
Micah Cowan wrote:
After another look at the relevant portions of the source code, it looks
like accept/reject rules are _always_ applied against the local
filename, contrary to what I'd been thinking. This needs to be changed.
(But it probably won't be, any time soon.
and
If something
This cleared up a lot. I really appreciate your reply. I've been using
the log and the server_response = on
parameters, but not --debug. I'll add that now and take a look, but
your 1..2..3.. answer below and the comment that accept/reject matching
is on the local filename explains what I'm se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Pattist wrote:
> Thank you for the quick response. Background is I'm on Windows XP, Gnu
> wget 1.11
>> This "doesn't affect traversal of HTML files" functionality is currently
>> implemented via a heuristic based on the filename extension. That i
Thank you for the quick response. Background is I'm on Windows XP, Gnu
wget 1.11
This "doesn't affect traversal of HTML files" functionality is currently
implemented via a heuristic based on the filename extension. That is, if
it ends in ".htm" or ".html", I believe, then it will be travers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Pattist wrote:
> I'm having trouble understanding how accept and reject work,
> particularly in the context of sites that rely on CGI and PHP to
> dynamically generate html pages. My questions relate to the following:
>
> 1) I don't fully unders
12 matches
Mail list logo
