Re: Semicolon not allowed in userinfo

2024-02-05 Thread Jeffrey Walton
When "c" is replaced by a > digit, Wget accepts the url and attempts to resolve "xyz". > > It's worth noting that both curl and aria2 accept the url example. > > Why is the semicolon not allowed in userinfo, despite the fact that other > special characte

Semicolon not allowed in userinfo

2024-02-05 Thread Bachir Bendrissou
e "xyz". It's worth noting that both curl and aria2 accept the url example. Why is the semicolon not allowed in userinfo, despite the fact that other special characters are allowed? Thank you, Bachir http://a;b:c@xyz

Re: Semicolon not allowed in userinfo

2024-01-29 Thread Bachir Bendrissou
Hi all, Thank you for your replies. The URL I posted is not the one you received and does not contain any space. The url may have been botched by the mailing list. I attach the url here for your reference. "http://a;b:c@xyz; Best, Bachir On Thu, Oct 5, 2023 at 9:47 PM Tim Rühsen wrote: > On

Re: Semicolon not allowed in userinfo

2023-10-05 Thread Tim Rühsen
On 10/4/23 14:04, Bachir Bendrissou wrote: Hi Tim, Wget doesn't follow the current specs and the parsing is lenient to accept some types of badly formatted URLs seen in the wild. Did you mean to say that the parsing is overly strict, and needs to be more permissive? I tried to make clear

Re: Semicolon not allowed in userinfo

2023-10-04 Thread Bachir Bendrissou
Hi Tim, Wget doesn't follow the current specs and the parsing is lenient to > accept some types of badly formatted URLs seen in the wild. > Did you mean to say that the parsing is overly strict, and needs to be more permissive? Because not allowing a semicolon is strict parsing, which needs to

Re: Semicolon not allowed in userinfo

2023-10-03 Thread Daniel Stenberg
On Tue, 3 Oct 2023, Tim Rühsen wrote: My version of curl (8.3.0) doesn't accept it: curl -vvv 'http://a ;b:c@xyz' * URL rejected: Malformed input to a URL function That's in no way a legal URL (accortding to RFC 3986) and it is not the semicolon that causes curl to reject it. It is the

Re: Semicolon not allowed in userinfo

2023-10-03 Thread Tim Rühsen
l the URL parsers are slightly different when it comes to edge cases. I'd consider curl as a good reference. Why is the semicolon not allowed in userinfo, despite that other special characters are allowed? First of all, userinfo does not allow spaces at all (look at https://datatracker.ietf.org/

Semicolon not allowed in userinfo

2023-10-02 Thread Bachir Bendrissou
Wget accepts the url and attempts to resolve "xyz". It's worth noting that curl and aria2 both accept the url example. Why is the semicolon not allowed in userinfo, despite that other special characters are allowed? Thank you, Bachir