feat(h2): h2c Upgrade from HTTP/1.1

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
networking

Research direction

The payload names no files or tests, so begin with the repository's HTTP/2 code and find where prior-knowledge cleartext connections are accepted. Then trace where an HTTP/1.1 request with an Upgrade: h2c header would be parsed and answered with a 101 response. Done means an upgrade request switches the connection to HTTP/2 and the existing HTTP/2 tests still pass. Confirm the scope with the maintainer first, since the issue marks this as low priority.

Written by the indexing model from the issue text.

Description

enhancement P2: later

HTTP/2 over cleartext works with prior knowledge only. Some servers (Node, Apache) and many clients use the Upgrade: h2c path (RFC 7540 §3.2, removed in RFC 9113 but still deployed). Low priority.

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.