quic: http/3 getting server settings and customSettings
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
For applications such as webtransport, http settings are important for negotiating capabilities.
The following problems may be present currently:
1.) I do not see a clear API path for a client that connects to a server to get the settings sent by the server.
Looking at the C++ code, I think the available settings could be on the SessionTicket,
However, if I immediately set a callback to onsessionticket after the Promise for QuicSession is fulfilled, I do not see a call.
@jasnell : Is there another API path to get this information? Or is this a bug, if I do not see the callback? Then I will try to make a test.
2.) nghttp3 does not seem to support settings beyond the settings hardcoded in the library. I will query upstream about implementing a mechanism similar to the customSettings mechanism currently used for http2.
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
Start by tracing the C++ QUIC implementation around SessionTicket and onsessionticket, then compare nghttp3’s hardcoded settings with HTTP/2’s customSettings mechanism. Confirm the intended API path for server settings and define tests for callback delivery and custom settings support; the issue is done when these behaviors have a clear implementation or upstream resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript, nodejs
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100