Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) from Anne van Kesteren on 2018-01-22 (public-webapps-github@w3.org from January 2018)

From: Anne van Kesteren <notifications@github.com>
Date: Mon, 22 Jan 2018 02:30:42 -0800
To: whatwg/url <url@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/url/issues/369/359383538@github.com>

`https://%6d%6D/%6d%6D?%6d%6D#%6d%6D` yields `https://mm/mm?%6d%6D#%6d%6D` in Chrome, meaning URL processors would still face the choices you suggest they'd no longer have to face if we change something here (or are you indeed proposing to normalize all and change Chrome as well?). Given that Edge normalizes the path too it seems reasonable to consider that though, but it does not really address your larger point, which I'm not quite sure I fully understand.

-- 
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/369#issuecomment-359383538

Received on Monday, 22 January 2018 10:31:04 UTC