uNetworking / uNetworking/uWebSockets

Disallow responding to http from an uncorked state (enforce use of res.cork)

Open
#1,516 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API-breaking v21
Dominant language
C++
Stars
19k
Forks
1.9k
Avg merge
3h 24m
Merged PRs (30d)
5

Description

Collecting all API-breaking ideas and issues

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue body only identifies a collection of API-breaking ideas and does not name files, tests, or an entry point. Start by locating the response handling and res.cork usage, then determine the intended enforcement behavior and add coverage showing that responding from an uncorked state is rejected.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
api, backend, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.