nginx/nginx

Deduplicate HTTP/2 code

Open

#1250 opened on Apr 5, 2026

View on GitHub
 (8 comments) (0 reactions) (2 assignees)C (30,331 stars) (7,903 forks)batch import
enhancementgood first issuerefined

Description

Feature Overview

Use common HTTP/2 code for the HTTP/2 server, HTTP/2 proxy, and GRPC.

Alternatives Considered

Continue having lots of duplicate code, which makes maintenance more difficult

Additional Context

The large amount of duplicate code means that bugs will need to be fixed in multiple places and new features are much harder to add.

Contributor guide

Tech stack
c
Domain
backendperformanceinfrastructure
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C programmingHTTP/2 protocolnginx architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
First, identify all HTTP/2 related code in the nginx source tree, likely in src/http/v2/ for the server, src/http/modules/ngx http proxy module.c for the proxy, and src/http/grpc/ for gRPC. Then, analyze the duplication patterns and design a common module that can be used by all three components. Consider existing abstractions like ngx http upstream round robin.c as a model. Finally, propose a refactoring plan and discuss with maintainers via the issue.