Re: Semicolon not allowed in userinfo

"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, > &g

Semicolon not allowed in userinfo

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 s

Re: Semicolon not allowed in userinfo

" wget: unable to resolve host address ‘xyz’ So, when the semicolon is included in *userinfo*, wget treats *userinfo* as part of the hostname. You can replicate this after disconnecting from your network first. Thank you, Bachir On Mon, Feb 5, 2024 at 10:08 PM Jeffrey Walton wrote: > On M

Semicolon not allowed in userinfo

Hi, The url attached example contains a semicolon in the userinfo segment. Wget rejects this url with the following error message: *Bad port number.* It seems that Wget sees "c" as a port number. When "c" is replaced by a digit, Wget accepts the url and attempts to resolve "xyz". It's worth no

Re: Semicolon not allowed in userinfo

sen wrote: > 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 t

Re: Semicolon not allowed in userinfo

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 b

Semicolon not allowed in userinfo

Hi, The following url example contains a semicolon in the userinfo segment: *http://a ;b:c@xyz* Wget rejects this url with the following error message: *http://a ;b:c@xyz: Bad port number.* It seems that Wget sees "c" as a port number. When "c" is replaced by a digit, Wget accepts the url and

URL query syntax

Hi, Are there any query strings that are invalid and should be rejected by the Wget parser? Wget seems to accept all sorts of strings in the query segment. For example: *"https://example.com/?a=ba=a "* The URL is accepted with no errors reported, despite missing a