Closed Bug 1689622 Opened 5 years ago Closed 5 years ago

HTTP3 fails to connect

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Version:
Firefox 87
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: neclimdul, Assigned: dragana)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36

Steps to reproduce:

Trying to connect to google and Youtube with Firefox nightly with http3 support enabled.

Actual results:

Long delay and a Secure Connection Failed error.

Expected results:

Pages should have loaded

Wasn't sure where to but some additional information based on the question/fields in the report form so here they are.

I confirmed that chrome works just fine and this was only happening inside the office building I work at. Looking into this further I logged into our firewall and was able to find corresponding denied "quic" packets on our firewall. It seems quic is not enabled in the protocol filtering and so is falling into the default deny rule.

I don't know the internals of firefox but it would seem that that deny just causes firefox to timeout and it doesn't have a way to fallback to http/http2 like chrome seems to do.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core

This sounds a lot like bug 1680688

Blocks: QUIC
Flags: needinfo?(dd.mozilla)

We have fallback mechanism, but maybe something is broken.
Can you please make a http log:
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

you can send the log to my email address, since the logs may contain cookies.

Thank you!

Flags: needinfo?(dd.mozilla) → needinfo?(neclimdul)
Assignee: nobody → dd.mozilla
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

This will be fixed by bug 1690008.

Can you retry? The bug should be fix now.

Sorry I completely forgot about getting you those logs. This does appear to be fixed. Thanks!

Steps to confirm:

  1. Enabled HTTP3 in experiments
  2. Navigated to google.com behind the problematic firewall
  3. Page loads without delay and I see HTTP/2 in the HTTP version in the network inspector.
Flags: needinfo?(neclimdul)
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.