Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675) from Alwin Blok on 2022-01-25 (public-webapps-github@w3.org from January 2022)

From: Alwin Blok <notifications@github.com>
Date: Tue, 25 Jan 2022 13:27:33 -0800
To: whatwg/url <url@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/url/issues/675/1021624767@github.com>

In any case. From the perspective of relative URLs, this is a good thing to do. The standard does not currently support parsing or serialising those, so decisions are often not checked against their implications for relative URLs either. 

This means that it is left up to implementors of URL manipulation libraries to define a customised version of WHATWG URL normalisation that avoids reparse bugs for relative URLs and avoids as much ambiguity around scheme dependent parsing behaviour as possible. 

Of course, the interpretation of `\` being scheme dependent means that tools that produce relative, scheme-less URLs would better escape such occurrences, even if that does not agree with the normalisation as specified in the WHATWG standard. On the plus side, URLs with occurrences of `\` are invalid, so I guess that isn’t so bad. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/675#issuecomment-1021624767

You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/675/1021624767@github.com>

Received on Tuesday, 25 January 2022 21:27:45 UTC