Re: [whatwg/url] Reparsing problem with non-special URL and double-dot path component (#415)

If I'm reading https://tools.ietf.org/html/rfc3986#section-5.2.2 correctly that has this problem as well. It forbids a scheme followed by an absolute path from taking the form `scheme://path` as that's ambiguous as it repeatedly points out (elsewhere in the document), but then `scheme:/doesnotmatter/..//path` is fine and would also yield this state.

https://tools.ietf.org/html/rfc3986#section-5.3 does not account for it either.

I suggested changing the host above, but upon re-reading this issue I rather like what Edge did here as it is isolated to serialization and preserves intent better.

-- 
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/415#issuecomment-626195881