feat(h2): accept server push on the client (optional)

Open
#46 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
22/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
c
Domain
networking

Research direction

Start from where the client sends the ENABLE_PUSH=0 setting and where PUSH_PROMISE is treated as a connection error; the issue names no files, so locate both by searching the HTTP/2 code for those names. The issue does not specify how the opt-in should be exposed, so settle that with maintainers first. Done means a client option that accepts pushed streams, with a test that covers a pushed response.

Written by the indexing model from the issue text.

Description

enhancement P2: later

The client sends ENABLE_PUSH=0 and treats PUSH_PROMISE as a connection error. Browsers dropped push, so this is fine by default. An opt-in for interop with servers that still push may be worth having. 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.