feat(h2h3): extended CONNECT (RFC 8441, RFC 9220)

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
networking

Research direction

Start in hreq.h, where the request validation lives, and find where the :protocol pseudo-header would need to be accepted. Then read the sans-IO HTTP/2 and HTTP/3 code to see how SETTINGS_ENABLE_CONNECT_PROTOCOL would be advertised and how a stream could act as a tunnel. Done means extended CONNECT works on both protocols, with tests that exercise the WebSocket handshake. Expect design decisions first, so discuss the approach on the issue before coding.

Written by the indexing model from the issue text.

Description

enhancement P2: later

Only classic CONNECT is supported. Extended CONNECT carries WebSockets over HTTP/2 and HTTP/3, and WebTransport builds on it.

SETTINGS_ENABLE_CONNECT_PROTOCOL, the :protocol pseudo-header in hreq.h's validation, and stream-as-tunnel semantics on both sides.

Dominant language
C
Stars
0
Forks
0
Avg merge
20h 4m
Merged PRs (30d)
25

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/cursed-http

All issues in public/cursed-http

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.