http-party/node-http-proxy

A full-featured http proxy for node.js

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 4th, 2026
Created on July 24th, 2010
Open Issues & Pull Requests: 619 (+0)
GitHub issues: Enabled
Number of forks: 1,998
Total Stargazers: 14,127 (+0)
Total Subscribers: 260 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.7 days
Mean response time: 183.6 days
90th percentile: 762.3 days
Tracked items: 29

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 29
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,126 days
Stale 30+ days: 28
Stale 90+ days: 27

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

node-http-proxy is an HTTP programmable proxying library that supports websockets and is suitable for implementing components such as reverse proxies and load balancers.

The tool addresses the need to intercept and forward HTTP requests between clients and target servers. It works by creating a proxy server instance through a createProxyServer call, which returns methods for proxying regular HTTP requests, WebSocket requests, and managing the server lifecycle. Requests flow through two pipelines—an incoming pipeline that manipulates the client-to-target stream and an outgoing pipeline that handles the target-to-client response stream. The library exposes both an Event Emitter API and a callback API for error handling, allowing developers to listen for proxy events and react to them programmatically.

Developers should choose this tool when building reverse proxies, load balancers, or other request-forwarding infrastructure in Node.js. It suits projects that need to modify request headers, rewrite responses, or handle WebSocket connections alongside standard HTTP traffic. The library can be used either as a standalone proxy server by invoking its listen method or integrated into existing HTTP servers for custom routing logic. HTTPS proxying is supported, and the tool provides options for configuring behavior across different proxy scenarios.

The project maintains active test coverage and demonstrates consistent development attention to code quality and reliability.