Closed Bug 1674449 Opened 6 years ago Closed 5 years ago

HTTP3 connection failures with low MTU

Categories

(Core :: Networking: HTTP, defect, P2)

Firefox 84
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: ekarulf, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36

Steps to reproduce:

We observed failures connecting to HTTP3 enabled sites when the MTU of the network path was below the minimum required for HTTP3 on IPv4 and IPv6 (1350 and 1370 respectively). The racing feature did not gracefully handle a truncated UDP response and fall back to HTTP2, resulting in a broken connection.

Repro steps:

  • Configure network MTU to something smaller than 1350, e.g. 1280
  • Install Firefox Nightly
  • Enable http3 in about:config
  • Try connecting to a HTTP3 enabled site www.youtube.com or http3.is

Actual results:

When connecting to a HTTP3 enabled site over a network link with a small MTU, the connection would fail with the error "error: secure connection failed"

Expected results:

The connection should have gracefully degraded to HTTP2 or HTTP1.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core
Blocks: QUIC
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]

This should be fix by bug 1674116

Blocks: 1653178
No longer blocks: QUIC

(In reply to Dragana Damjanovic [:dragana] from comment #1)

This should be fix by bug 1674116

It sis a wrong bug number (the bugs are duplicate), the bug thatt will fix this is bug 1675016.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.