Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?

[Daniel Stenberg <[e-mail]>]

On Fri, 16 Jan 2015, [e-mail] wrote:

> Here is something that round-trips a URL parse/stringify transformation, and 
> actually works, despite being an invalid URI and invalid IRI:
>
>  https://www.google.com/?q=[z]
>
> My gut feeling is that allowing this to be valid is a possible change, as 
> I've said. I appreciate this is at odds with RFC 3986, but if URL parsers do 
> generally ignore the error that's fine.
̈́
$ curl 'https://www.google.com/?q=[z]'
curl: (3) [globbing] bad range in column 32

This isn't strictly the URI parser saying this, but since we know that [] are 
not legal in a URI we (curl developers) could use them for additional 
functionality...

Just suggesting that changing this will make some things break.

-- 

  / daniel.haxx.se