Closed Bug 1635502 Opened 4 years ago Closed 4 years ago

Setting network.http.http3.enabled to TRUE isn't picked up right away

Categories

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

Product:
Core
Component:
Networking: HTTP
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: grover, Assigned: dragana)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

  1. Set network.http.http3.enabled to true and restart the browser
  2. open Network Activity webtools pane. Add protocol column.
  3. visit https://cloudflare-quic.com/ Protocol should show HTTP/3, if not initially, then on refresh.
  4. In another tab, set network.http.http3.enabled to false
  5. Refresh the page. Protocol now shows as HTTP/2 (good so far)
  6. Set network.http.http3.enabled to true
  7. Refresh the page. Protocol still shows as HTTP/2.

Ideally, changing the pref should cause HTTP/3 to be attempted for existing pages if refreshed.

This should save testers time as we look to more broadly roll out HTTP/3 support, and will cause the off->on case to behave the same as the on->off case.

The severity field is not set for this bug.
:grover, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(agrover)

(In reply to Andy Grover [:grover] from comment #0)

  1. Set network.http.http3.enabled to true and restart the browser
  2. open Network Activity webtools pane. Add protocol column.
  3. visit https://cloudflare-quic.com/ Protocol should show HTTP/3, if not initially, then on refresh.
  4. In another tab, set network.http.http3.enabled to false
  5. Refresh the page. Protocol now shows as HTTP/2 (good so far)
  6. Set network.http.http3.enabled to true
  7. Refresh the page. Protocol still shows as HTTP/2.

Ideally, changing the pref should cause HTTP/3 to be attempted for existing pages if refreshed.

This should save testers time as we look to more broadly roll out HTTP/3 support, and will cause the off->on case to behave the same as the on->off case.

Actually, I do not want to change the current behavior. Also with HTTPSSVC it will be easier.

AltSvc record for HTTP3 is not put into cache if http3 is disabled and it will be removed if found in the cache and http3 is disabled. I am not really convince this is helpful for testing.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX

ok, thanks for taking a look.

Flags: needinfo?(agrover)
You need to log in before you can comment on or make changes to this bug.