Valentin Gosu

The change happened as a consequence of [Bug 1724233 - IDNA does not conform to RFC and is interpreted as a different hostname](https://bugzilla.mozilla.org/show_bug.cgi?id=1724233).

@annevk rust-url fuzzing has found another test case for IDNA that doesn't round-trip: `http://a.xn--xn-----/` | input | output | Live URL Viewer | | --- | -- | -- |...

> @valenting @mozfreddyb do either of you know what Gecko does for `text/html` responses? Do they get sniffed for feeds as the MIME Sniffing standard suggests in step 5 of...

> At least in the case of Chrome, if the Priority header is set before it gets to the networking stack then the user-supplied value will be used (like was...

> as best as I could tell, the change in Firefox 126 is still only setting the header in HTTP/3 No, the Priority header is all requests. You can check...

Firefox changes tracked in [bug 1340200](https://bugzilla.mozilla.org/show_bug.cgi?id=1340200)

> In fact the only HTTP/1.1 implementation I am aware of is [Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1813035#c6), but this still has not been enabled by default. Indeed Firefox accepts early hints over HTTP/1.1, but...

I don't have any concerns regarding this change. I'm happy to standardize on a common list of blocked ports. Here are the ports [currently blocked in Gecko](https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/netwerk/base/nsIOService.cpp#104)

I think there are two different issues with these schemes. 1. Schemes that wrap another URL with the intention of passing that URL to an external protocol handler. 2. Schemes...

> As an example, `http://[::1%32]/` is currently failure per the URL Standard (and Gecko & WebKit), but `http://[::12]/` in Chromium. After the proposed change it would be `http://[[::1]/`. I'd rather...