Hey Bachir,
thank you for going into the details and bringing up the concerns and
also for keeping pushing.
I just pushed ed0c7c7e0e8f7298352646b2fd6e06a11e242ace to fix the
issue.
Indeed, the URL parser implementation of wget 1.x is based on RFC 2396,
a standard from 1998.
But even by this
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 dis
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
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
replicate this after disconnecting from
> your network first.
>
My bad, I was only answering the question, "Why is the semicolon not
allowed in userinfo, despite the fact that other special characters are
allowed?"
I did not try to figure out what was wrong with the script.
Jeff
get 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 both curl and aria2 accept the url example.
> >
> > Why is the semicolon not allowed
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 cha
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
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
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 t
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
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 spac
put to a URL function
All 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
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
14 matches
Mail list logo
