First release: priorities
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- c
- Domain
- networking, performance
Research direction
This is a roadmap, not a single task, so there is no file or test named here. Read the P0 items first (#32 QUIC Retry, #33 Version Negotiation, #36 pacing), each as its own linked issue, to see what each one needs. Work on this issue is done when the first release is cut with the P0 and P1 items complete; the P2 items are out of scope for a first newcomer contribution.
Written by the indexing model from the issue text.
Description
The order to work through for a first release of the HTTP/1.1, HTTP/2 and HTTP/3 clients and servers. Correctness against real servers and networks comes first, then latency and efficiency, then new protocol features.
P0: release blockers
- #32 QUIC client handling of Retry. Without it, servers that validate addresses (common under load and behind CDNs) can't be reached at all.
- #33 Version Negotiation on the client. Today the handshake times out instead of failing at once.
- #36 Pacing. Sending a whole congestion window in one burst causes avoidable loss on real paths. A library others ship should behave well on the network by default.
P1: in the first release
- #35 TLS + ALPN for the HTTP/2 client example, tested against real servers. Real-world HTTP/2 is all TLS.
- #44 Stateless reset detection. It's small, and makes server restarts fail fast.
- #43 Connection ID rotation. At minimum, honouring the peer's NEW_CONNECTION_ID /
retire_prior_to(the spec requires it). Full migration can come later. - #34 0-RTT and session resumption. The largest latency win.
- #39 Blocked streams in our QPACK decoder. Browsers' first request bursts to our server get compressed.
- #37 Path MTU discovery. About 15% fewer packets on bulk transfers.
- #40 Extensible priorities. Lets pages load in a sensible order.
P2: later
#38 ECN, #41 extended CONNECT (WebSockets), #42 DATAGRAM and HTTP datagrams, #47 BBR, #45 h2c Upgrade, #46 accepting server push.
- Dominant language
- C
- Stars
- 0
- Forks
- 0
- Avg merge
- 20h 4m
- Merged PRs (30d)
- 25
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from public/cursed-http
-
P0: release blocker
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
public/cursed-http#56 ·
Maintainers usually reply within 1 day
-
P1: first release
Difficulty 5/5 Over a week Newbie friendliness 15/100
public/cursed-http#61 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 4/5 3-5 days Newbie friendliness 35/100
public/cursed-http#60 ·
Maintainers usually reply within 1 day
-
documentation P0: release blocker
Difficulty 3/5 1-2 days Newbie friendliness 42/100
public/cursed-http#59 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 4/5 3-5 days Newbie friendliness 35/100
public/cursed-http#58 ·
Maintainers usually reply within 1 day
All issues in public/cursed-http
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
xerial/sqlite-jdbc#1515 ·
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·
-
compiler-rt:asan
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
llvm/llvm-project#242921 ·
Maintainers usually reply within 1 day
-
Missing gcc __builtin_stdc_bit_width/floor/ceil signature makes intellisense wrongly report error 70Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
microsoft/vscode-cpptools#14874 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FujiNetWIFI/fujinet-firmware#2401 ·
Maintainers usually reply within 1 day