Remember this fun URL from three years ago?
https://daniel.haxx.se/blog/2022/09/08/http-http-http-http-http-http-http/
undefined
daniel:// stenberg://
@bagder@mastodon.social
Post
-
Remember this fun URL from three years ago? -
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.@dascandy @suzannealdrich @jbqueru I'm sorry but already while I worked at Mozilla and Firefox my colleagues were in team WHATWG and I'm pretty sure they still are.
And doing a standard for URLs without having the super powers involved and interested is obviously not going to make a successful spec
-
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.@dascandy @suzannealdrich @jbqueru add port numbers, IP addresses (v4, v6, zone id?), add options? How about IDN?
I see you used two slashes, but URIs actually don't have that. Many have no slashes at all.
But sure, everything *could* be written down in a spec. Getting the world to agree with that spec though: not so easy.
-
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.@dascandy @suzannealdrich @jbqueru we could theoretically do that, sure.
-
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.@suzannealdrich @jbqueru and its impossible to be perfectly compliant because then suddenly the "spec" changes and you're not anymore. Not a way to build things like URLs that are supposed to in theory be possible to outlive us all.
-
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.@jbqueru I've been told in discussions with WHATWG people that their specs (they call them specs) are both: documents how browsers work and they say how browsers should work. When I've pointed out discrepancies in the past (browsers that didn't follow their spec), the answer have usually been that it will be fixed in a future browser release and that the spec is right.
-
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.I've said it before. The WHATWG won't fix this because they are happy with a spec that works for them and they don't care about URLs for the rest of the world.
The IETF has given up the topic, partly I think because WHATWG already has stated that they run their own race and making a unified spec that works would be next to impossible.
-
Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.Having ongoing discussions about URL parsing differences as a basis for a #curl security vulnerability report made me check when I wrote my "my URL isn't your URL" blog post.
*Nine years ago*. And we have not made a single move towards a solution in all this time.
https://daniel.haxx.se/blog/2016/05/11/my-url-isnt-your-url/
-
On September 28, I will speak at #EuroBSDCon in Zagreb Croatia.On September 28, I will speak at #EuroBSDCon in Zagreb Croatia.
But more importantly, I will bring #curl stickers.
-
The Serial Port made this lovely IRC documentaryIRC has a special place in my heart: https://un.curl.dev/mine/dancer.html
-
The Serial Port made this lovely IRC documentaryThe Serial Port made this lovely IRC documentary
(and yes, I got a "thanks" in the ending credits as I contributed with facts)