When did we jump to HTTP3!... i've not been paying attention to the protocol space there clearly..

oh. it's a new name for QUIC..

Should it be working on Edge Canary as well?

freitasm: Check Edge notes. I don't know if it has it.

This is exactly what I ended up doing and it does appear to be in Edge. - edge://flags/#enable-quic

Yes, Just searched and it seems Edge inherits HTTP/3 from Chromium. Firefox should add it to dev later this quarter, and Opera will have it as well.

freitasm:

Yes, Just searched and it seems Edge inherits HTTP/3 from Chromium. Firefox should add it to dev later this quarter, and Opera will have it as well.

@hio77:

freitasm:

 

Yes, Just searched and it seems Edge inherits HTTP/3 from Chromium. Firefox should add it to dev later this quarter, and Opera will have it as well.

 

 

Firefox is too busy planning how to break end user experience with a DoH moment...

 

DoH breaks Air NZ Koru lounge access and in-flight WiFi because they completely block traffic before authentication - and users can't access the authentication page because there's no DNS resolution if using DoH or Private DNS (on Android 9 and above). You should tell this to the folks managing the Air NZ system or you will see more complaints on Herald and Stuff than Spark Sport.

freitasm:

@hio77:

freitasm:

Yes, Just searched and it seems Edge inherits HTTP/3 from Chromium. Firefox should add it to dev later this quarter, and Opera will have it as well.

Firefox is too busy planning how to break end user experience with a DoH moment...

DoH breaks Air NZ Koru lounge access and in-flight WiFi because they completely block traffic before authentication - and users can't access the authentication page because there's no DNS resolution if using DoH or Private DNS (on Android 9 and above). You should tell this to the folks managing the Air NZ system or you will see more complaints on Herald and Stuff than Spark Sport.

freitasm:

 

@hio77:

freitasm:

 

Yes, Just searched and it seems Edge inherits HTTP/3 from Chromium. Firefox should add it to dev later this quarter, and Opera will have it as well.

 

 

Firefox is too busy planning how to break end user experience with a DoH moment...

 

 

DoH breaks Air NZ Koru lounge access and in-flight WiFi because they completely block traffic before authentication - and users can't access the authentication page because there's no DNS resolution if using DoH or Private DNS (on Android 9 and above). You should tell this to the folks managing the Air NZ system or you will see more complaints on Herald and Stuff than Spark Sport.

 

Have you tested this? Firefox has some smarts around edge cases like this to prevent breakage, though I lack the means to test myself. Also, DoH is only being turned on for the US right now.

Also, the DNS admin can disable FFx DoH network-wide right now by NXDOMAINing use-application-dns.net. If folks had spent 5 minutes reading documentation, a lot less FUD would have been dumped on the internet around this issue...

 

 

 

As a precaution, Firefox features a system that detects if a name can’t be resolved at all with TRR and can then fall back and try again with just the native resolver (the so called TRR-first mode). Ending up in this scenario is of course slower and leaks the name over clear-text UDP but this safety mechanism exists to avoid users risking ending up in a black hole where certain sites can’t be accessed. Names that causes such TRR failures are then put in an internal dynamic blacklist so that subsequent uses of that name automatically avoids using DNS-over-HTTPS for a while (see the blacklist-duration pref to control that period). Of course this fall-back is not in use if TRR-only mode is selected.

 

Via https://daniel.haxx.se/blog/2018/06/03/inside-firefoxs-doh-engine/

I am using the Edge canary build and have enabled QUIC (thanks @brumfondl).

Seems to be a bit... snappier? But for some reason I can't login. Keep getting turfed to the main forum index after accepting my creds.

Annnndddd now I am being rate-limited.

ShinyChrome:

 

I am using the Edge canary build and have enabled QUIC (thanks @brumfondl).

 

Seems to be a bit... snappier? But for some reason I can't login. Keep getting turfed to the main forum index after accepting my creds.

 

Annnndddd now I am being rate-limited.

 

NVM for some reason Edge was blocking cookies for everything by default.

After cruising around yesterday and today, it does feel that extra bit snappier.

Edit: Running Edge Beta and Canary side-by-side looking at the dev tools network panel, canary is a good 1-2s faster on average to load

hio77:

When did we jump to HTTP3!