Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)

The concern about focusing only in browsers is real and there are evidence of problems that happened because of that. Last year I found out that ietf [created an RFC for cookies in 2011](https://www.ietf.org/mail-archive/web/http-state/current/msg01461.html) documenting the allowed characters in a cookie name without considering the internals of server-side technologies such as PHP. That created a [big interoperability issue](https://github.com/js-cookie/js-cookie/blob/f2b25713e8fae658d418b60710adc0e0d14998d9/SERVER_SIDE.md#php), because php decoding implementation is coupled to a historic syntax (`$_COOKIE`) that is older than many browsers and therefore cannot change, ever. This heavily restricted the default interoperability between client and server-side transmission of unicode characters using UTF-8, just because the spec was built only for browsers.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/118#issuecomment-219266156