Re: [apps-discuss] RFC6454 "the web origin concept" obsoleted?

[Daniel Stenberg <[e-mail]>]

On Mon, 18 Jul 2016, [e-mail] wrote:

> * Are the changes to RFC3986 & RFC3987 evidenced in [URL] widely applicable 
> to all URL-utilizing specs and if so, do we obsolete them and point to 
> [URL], or backport the changes to RFC3986bis & RFC3987bis? Or do something 
> else, or do nothing?

The [URL] spec is mostly followed by browsers while the rest of the URL 
parsing world is all over the place but very few non-browsers implement the 
[URL] spec and instead do various mixes of what the RFCs say and the browsers 
do. I blogged about this exact issue a short while ago [1] after having 
realized the [URL] spec says eight thousand slashes in a HTTP URL is fine and 
should be parsed.

I personally am not a fan of neither the [URL] spec style (I find it very hard 
to read), how it is being written or what it says a URL can look like. But I 
know I get a lot of objections and "web compatibility" arguments thrown at me 
when I say so...

So the RFCs are currently lacking a lot when it comes to parsing modern URLs, 
but the [URL] spec is not even trying to make a spec for an entire web 
infrastructure so it isn't a generic solution either. I don't have a good 
answer for where we should go from here.

[1] = https://daniel.haxx.se/blog/2016/05/11/my-url-isnt-your-url/

-- 

  / daniel.haxx.se