Closed Bug 1800614 Opened 2 years ago Closed 2 years ago

ohttp: Serialize and deserialize ohttp using rfc9292

Categories

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

Product:
Core
Component:
Networking: HTTP
Type:
task

Tracking

()

Status:
RESOLVED MOVED

People

(Reporter: valentin, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

rfc9292 introduces a serialization format for HTTP requests and responses.
This format is supposed to be used to serialize the inner payload that we then encrypt and send to the relay.

The ohttp crate also has a bhttp implementation, that we can add xpcom bindings for - either in bug 1799026 or in a separate bug.

There are 2 ways forward here:

  1. Introduce nsIHttpChannel implementation that serializes itself and passes that serialization to a second channel in AsyncOpen.
  2. change TRR::SendHTTPRequest and ODoHDNSPacket::Decode to do the de/serialization.

Long term we should do 1, but no. 2 should work reasonably well for now.

Bug 1815741 already made this quite generic. Now it's just a matter of using it if necessary.

Priority: P2 → P3

Fixed by bug 1815741.

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