quic: http/3 datagrams partially diverge from spec
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Http datagrams are according to spec composed as:
HTTP/3 Datagram {
Quarter Stream ID (i),
HTTP Datagram Payload (..),
}
and beside this a normal quic datagram.
If I understand the current implementation correctly, the quarter stream id of the bidirectional stream is not included,
and just unfiltered quicdatagrams are sent.
Of course, it is not difficult to sort this issue out on js side, but may be users may stumble upon this.
@jasnell @pimterry what do you think?
Implementing this would not be really hard.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or test. Start by locating Node.js's QUIC and HTTP/3 datagram implementation, then compare its framing with the HTTP/3 Datagram structure quoted here. Done means bidirectional datagrams include the quarter stream ID while ordinary QUIC datagrams remain distinct; run the relevant existing tests after locating them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100