Closed Bug 1792678 Opened 2 years ago Closed 2 years ago

WebTransport and HTTP redirects

Categories

(Core :: Networking: HTTP, task, P3)

task

Tracking

()

RESOLVED FIXED
110 Branch
Tracking Status
firefox110 --- fixed

People

(Reporter: dragana, Assigned: smayya)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

The current implementation (bug 1790398) supports redirects and it will follow them, although the tests are still outstanding.

The spec is not concrete yet and there was some discussion on the IETF.

This bug should make sure we add tests for redirects and also add a pref to control the behavior and when the decision is made on IETF disable or enable redirects.

Assignee: nobody → smayya

Kershaw I would like to confirm my understanding of the bug and my approach to solve it. Please let me know if I have missed something.

Changes for this bug includes 2 parts
Part 1 -

  • Add a preference for controlling redirects
  • The pref can be checked here

Part 2

  • Add a test case for redirect similar to test_connect_wt , replacing success in the path with redirect.
  • Ensure the redirect is handled here
  • Currently we only support 200 and 404 as responses to a web transport request for accepting/rejecting the request. We need to extend this to support redirects and other responses. The following functions will be affected
  • response
  • webtransport_session_accept
Flags: needinfo?(kershaw)

(In reply to Sunil Mayya from comment #1)

Kershaw I would like to confirm my understanding of the bug and my approach to solve it. Please let me know if I have missed something.

Thanks Sunil! These all look good to me.

Changes for this bug includes 2 parts
Part 1 -

  • Add a preference for controlling redirects
  • The pref can be checked here

Yes, I think this is a correct place.

Part 2

  • Add a test case for redirect similar to test_connect_wt , replacing success in the path with redirect.
  • Ensure the redirect is handled here
  • Currently we only support 200 and 404 as responses to a web transport request for accepting/rejecting the request. We need to extend this to support redirects and other responses. The following functions will be affected
  • response
  • webtransport_session_accept

According to the discussion here, it seems they inclined to not support redirection. But even so, we still need to write a test for this.
I think modifying response and webtransport_session_accept to support returning 3xx response (also a location header) would be the first step.
To do this, you may want to create a neqo issue and submit a PR.
Thanks!

Flags: needinfo?(kershaw)

Neqo issue created to track support of 3XX response header here. Changes are verified locally and PR will be submitted soon.

Attachment #9310113 - Attachment description: WIP: Bug 1792678 - add webtransport redirect preference → Bug 1792678 - add webtransport redirect preference. r=#necko
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/autoland/rev/90a70d71e836 add webtransport redirect preference. r=necko-reviewers,kershaw
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: