- From: Timothy Gu <notifications@github.com>
- Date: Mon, 13 Feb 2023 10:20:06 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 13 February 2023 18:20:19 UTC
I tested a range of parsers: * For non-special schemes (which is where URL code points are used in the parser): * No one ever escapes `[` and `]` in path, query, and fragment * No one ever escapes `[` and `]` in host, but: * Only Go, Chrome, Python urlparse accept it * Python urllib3, libcurl, and current spec reject it as invalid * Node.js' legacy `url` parser does something weird (inserts a `/` before the `[`) * For special schemes: * Only Python urllib3 escapes `[` and `]` in path, query, and fragment * FWIW this seems to be a relatively new behavior * No one ever escapes `[` and `]` in host, but: * Only Go, Chrome, Python urlparse accept it -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/753#issuecomment-1428438386 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/753/1428438386@github.com>
Received on Monday, 13 February 2023 18:20:19 UTC