Re: Semicolon not allowed in userinfo

[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 that it is not the semicolon.
What was unclear?

> Also, as Daniel pointed out, your curl input example appears to have a
> space.

Sorry, the curl URL was no mine, it was yours. May I cite the URL from 
your original email? There is a space, no?

> *http://a <http://a>;b:c@xyz*

Regards, Tim

> Bachir
>
> On Tue, Oct 3, 2023 at 1:45 PM Daniel Stenberg <daniel@haxx.se> wrote:
>
> > On Tue, 3 Oct 2023, Tim Rühsen wrote:
> >
> > > My  version of curl (8.3.0) doesn't accept it:
> > >
> > > curl -vvv 'http://a <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 space.
> >
> > But I don't know if that is maybe your clients or the mailing list
> > software
> > that botched it so badly?
> >
> > --
> >
> >    / daniel.haxx.se

OpenPGP_signature.asc
Description: OpenPGP digital signature