Re: Semicolon not allowed in userinfo

Tim Rühsen <[email protected]> Sat, 1 Jun 2024 18:42:29 +0200

Newsgroups	gmane.comp.web.wget.general
Message-ID	<[email protected]>

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 the userinfo segment.
> 
> In the example, wget does not recognise the userinfo segment, and
> instead treats it as part of the hostname. When the semicolon is
> removed, the userinfo is recognised and is no longer processed as
> hostname. The rejection of semicolons in userinfo creates a parsing
> discrepancy with other URL parsers.
> 
> curl "a;bc@xyz"
> curl: (6) Could not resolve host: xyz
> 
> wget "a;bc@xyz"
> wget: unable to resolve host address ‘a;bc@xyz’
> 
> wget "abc@xyz"
> wget: unable to resolve host address ‘xyz’
> 
> You can replicate the above cases after disconnecting from your DNS.
> 
> Thank you,
> Bachir
>

OpenPGP_signature.asc (application/pgp-signature, 840 B)