Hi,

The following url example contains a semicolon in the userinfo segment:


*http://a <http://a>;b:c@xyz*
Wget rejects this url with the following error message:

*http://a <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 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

Reply via email to