Hi Tim,
Thank you for your email.
First, the current behavior of wget 1.x contradicts the URI standard
defined in RFC 3986, which allows semicolons in the userinfo segment.
Ensuring compliance with this widely accepted standard is essential
for *interoperability
and correctness*.
Second, the
Hi Tim,
Am Sat, 1 Jun 2024 18:57:00 +0200
schrieb Tim Rühsen :
> Wget sets the remote time when using the -N / --timestamping option.
Hm, that is related to comparing local and remote timestamps for
deciding to re-download a file or not (I read in the man page). How is
that related to wget not
Hey Thomas,
thanks for your report.
Wget sets the remote time when using the -N / --timestamping option.
> Is a fix in wget 1.x something to be considered at this point in time?
Yes, if we find a volunteer to make up a patch.
> FTP support seems to be dropped altogether from Wget 2
Hi Bachir,
wget2 "a;bc@xyz"
wget2: Failed to resolve 'xyz' (Name or service not known)
Is there a real-life problem that requires wget 1.x to accept a
semicolon in the userinfo field?
Regards, Tim
On 5/14/24 12:42, Bachir Bendrissou wrote:
Hi,
The URL example below contains a semicolon in
Hey David,
> It appears that wget2 is getting files outside of what my regex-es
allow, but on closer inspection, the files don't exist on my FS.
Indeed, wget2 is acting slightly different to wget.
In this case, wget2 fetches URLs from pages outside your regex, but will
only store those
