http-proxy-middleware README

The project's README from github.com/chimurai/http-proxy-middleware. As one markdown file: README.md.

http-proxy-middleware

GitHub Workflow Status (with branch) Coveralls Known Vulnerabilities npm

Node.js proxying made simple. Configure proxy middleware with ease for connect, express, next.js, hono and many more.

Powered by httpxy. A maintained version of http-proxy.

⚠️ Note

This page is showing documentation for version v4.x.x (release notes)

For older documentation:

TL;DR

Proxy /api requests to http://www.example.org

:bulb: Tip: Set the option changeOrigin to true for name-based virtual hosted sites.

// typescript
import express from 'express';
import type { NextFunction, Request, Response } from 'express';
import { createProxyMiddleware } from 'http-proxy-middleware';
import type { Filter, Options, RequestHandler } from 'http-proxy-middleware';

const app = express();

const proxyMiddleware = createProxyMiddleware<Request, Response>({
  target: 'http://www.example.org/api',
  changeOrigin: true,
});

app.use('/api', proxyMiddleware);

app.listen(3000);

// proxy and keep the same base path "/api"
// http://127.0.0.1:3000/api/foo/bar -> http://www.example.org/api/foo/bar

All httpxy options can be used, along with some extra http-proxy-middleware options.

Table of Contents

Install

npm install --save-dev http-proxy-middleware

Basic usage

Create and configure a proxy middleware with: createProxyMiddleware(config).

import { createProxyMiddleware } from 'http-proxy-middleware';

const apiProxy = createProxyMiddleware({
  target: 'http://www.example.org',
  changeOrigin: true,
});

// 'apiProxy' is now ready to be used as middleware in a server.

Express Server Example

An example with express server.

// include dependencies
import express from 'express';
import { createProxyMiddleware } from 'http-proxy-middleware';

const app = express();

// create the proxy
/** @type {import('http-proxy-middleware').RequestHandler<import('express').Request, import('express').Response>} */
const exampleProxy = createProxyMiddleware({
  target: 'http://www.example.org/api', // target host with the same base path
  changeOrigin: true, // needed for virtual hosted sites
});

// mount `exampleProxy` in web server
app.use('/api', exampleProxy);
app.listen(3000);

app.use(path, proxy)

If you want to use the server's app.use path parameter to match requests. Use pathFilter option to further include/exclude requests which you want to proxy.

app.use(
  createProxyMiddleware({
    target: 'http://www.example.org/api',
    changeOrigin: true,
    pathFilter: '/api/proxy-only-this-path',
  }),
);

app.use documentation:

Options

http-proxy-middleware options:

pathFilter (string, []string, glob, []glob, function)

Narrow down which requests should be proxied. The path used for filtering is the request.url pathname. In Express, this is the path relative to the mount-point of the proxy.

pathRewrite (object/function)

Rewrite target's url path. Object-keys will be used as RegExp to match paths.

// rewrite path
pathRewrite: {'^/old/api' : '/new/api'}

// remove path
pathRewrite: {'^/remove/api' : ''}

// add base path
pathRewrite: {'^/' : '/basepath/'}

// custom rewriting
pathRewrite: function (path, req, res, options) { return path.replace('/api', '/base/api') }

// custom rewriting, returning Promise
pathRewrite: async function (path, req, res, options) {
  const should_add_something = await httpRequestToDecideSomething(path);
  if (should_add_something) path += "something";
  return path;
}

// `res` is undefined in WebSocket upgrade flows.

router (object/function)

Re-target option.target for specific requests.

// Use `host` and/or `path` to match requests. First match will be used.
// The order of the configuration matters.
router: {
    'integration.localhost:3000' : 'http://127.0.0.1:8001',  // host only
    'staging.localhost:3000'     : 'http://127.0.0.1:8002',  // host only
    'localhost:3000/api'         : 'http://127.0.0.1:8003',  // host + path
    '/rest'                      : 'http://127.0.0.1:8004'   // path only
}

// Custom router function (string target)
router: function(req, res, options) {
    return 'http://127.0.0.1:8004';
}

// Custom router function (target object)
router: function(req, res, options) {
    return {
        protocol: 'https:', // The : is required
        host: '127.0.0.1',
        port: 8004
    };
}

// Asynchronous router function which returns promise
router: async function(req, res, options) {
    const url = await doSomeIO();
    return url;
}

// NOTE: `res` is undefined in WebSocket upgrade flows.

plugins (Array)

const simpleRequestLogger = (proxyServer, options) => {
  proxyServer.on('proxyReq', (proxyReq, req, res) => {
    console.log(`[HPM] [${req.method}] ${req.url}`); // outputs: [HPM] GET /users
  });
},

const config = {
  target: `http://example.org`,
  changeOrigin: true,
  plugins: [simpleRequestLogger],
};

ejectPlugins (boolean) default: false

If you're not satisfied with the pre-configured plugins, you can eject them by configuring ejectPlugins: true.

NOTE: register your own error handlers to prevent server from crashing.

// eject default plugins and manually add them back
import {
  debugProxyErrorsPlugin, // subscribe to proxy errors to prevent server from crashing
  errorResponsePlugin, // return 5xx response on proxy error
  loggerPlugin, // log proxy events to a logger (ie. console)
  proxyEventsPlugin, // implements the "on:" option
} from 'http-proxy-middleware';

createProxyMiddleware({
  target: `http://example.org`,
  changeOrigin: true,
  ejectPlugins: true,
  plugins: [debugProxyErrorsPlugin, loggerPlugin, errorResponsePlugin, proxyEventsPlugin],
});

definePlugin helper

Create your own http-proxy-middleware plugin.

(Default plugins are created with definePlugin)

import { createProxyMiddleware, definePlugin } from 'http-proxy-middleware';

const myPlugin = definePlugin((proxyServer, options) => {
  // plugin implementation
});

// use configure and use plugin
createProxyMiddleware({
  target: `http://example.org`,
  plugins: [myPlugin],
});

logger (Object)

Configure a logger to output information from http-proxy-middleware: ie. console, winston, pino, bunyan, log4js, etc...

Only info, warn, error are used internally for compatibility across different loggers.

If you use winston, make sure to enable interpolation: https://github.com/winstonjs/winston#string-interpolation

See also logger recipes (recipes/logger.md) for more details.

createProxyMiddleware({
  logger: console,
});

httpxy events

Subscribe to httpxy events with the on option:

createProxyMiddleware({
  target: 'http://www.example.org',
  on: {
    proxyReq: (proxyReq, req, res) => {
      /* handle proxyReq */
    },
    proxyRes: (proxyRes, req, res) => {
      /* handle proxyRes */
    },
    error: (err, req, res) => {
      /* handle error */
    },
  },
});

httpxy options

The following options are provided by the underlying httpxy library.

WebSocket

See recipes/websocket.md for more examples.

// verbose api
createProxyMiddleware({ pathFilter: '/', target: 'http://echo.websocket.org', ws: true });

External WebSocket upgrade

In the previous WebSocket examples, http-proxy-middleware relies on an initial HTTP request in order to listen to the HTTP upgrade event. If you need to proxy WebSockets without the initial HTTP request, you can subscribe to the server's HTTP upgrade event manually.

When the same middleware instance is attached to multiple servers and ws: true is used, each server needs its own initial HTTP request before upgrades are auto-subscribed.

const wsProxy = createProxyMiddleware({ target: 'ws://echo.websocket.org', changeOrigin: true });

const app = express();
app.use(wsProxy);

const server = app.listen(3000);
server.on('upgrade', wsProxy.upgrade); // <-- subscribe to http 'upgrade'

Intercept and manipulate requests

Intercept requests from downstream by defining on.proxyReq in createProxyMiddleware.

Fix POST request:

Use the pre-provided request interceptor fixRequestBody to fix proxied POST requests when bodyParser is applied before this middleware.

import { createProxyMiddleware, fixRequestBody } from 'http-proxy-middleware';

const proxy = createProxyMiddleware({
  on: {
    // Fix POST request when `bodyParser` is used
    proxyReq: fixRequestBody,
  },
});

Modify POST request:

import bodyParser from 'body-parser';
import { createProxyMiddleware, fixRequestBody } from 'http-proxy-middleware';

app.use(bodyParser.json());

app.use(
  '/api',
  createProxyMiddleware({
    target: 'http://www.example.org',
    changeOrigin: true,
    on: {
      proxyReq: (proxyReq, req) => {
        if (req.method !== 'POST' || !req.body) {
          return;
        }

        // mutate parsed request body
        req.body.injected = 'server-only';

        // write mutated body to the proxied request
        fixRequestBody(proxyReq, req);
      },
    },
  }),
);

Intercept and manipulate responses

Intercept responses from upstream with responseInterceptor. (Make sure to set selfHandleResponse: true)

Responses which are compressed with brotli, gzip and deflate will be decompressed automatically. The response will be returned as buffer (docs) which you can manipulate.

With buffer, response manipulation is not limited to text responses (html/css/js, etc...); image manipulation will be possible too. (example)

NOTE: responseInterceptor disables streaming of target's response.

Example:

import { createProxyMiddleware, responseInterceptor } from 'http-proxy-middleware';

const proxy = createProxyMiddleware({
  /**
   * IMPORTANT: avoid res.end being called automatically
   **/
  selfHandleResponse: true, // res.end() will be called internally by responseInterceptor()

  /**
   * Intercept response and replace 'Hello' with 'Goodbye'
   **/
  on: {
    proxyRes: responseInterceptor(async (responseBuffer, proxyRes, req, res) => {
      const response = responseBuffer.toString('utf8'); // convert buffer to string
      return response.replace('Hello', 'Goodbye'); // manipulate response and return the result
    }),
  },
});

Check out interception recipes for more examples.

Node.js 17+: ECONNREFUSED issue with IPv6 and localhost (#705)

Node.js 17+ no longer prefers IPv4 over IPv6 for DNS lookups. E.g. It's not guaranteed that localhost will be resolved to 127.0.0.1 – it might just as well be ::1 (or some other IP address).

If your target server only accepts IPv4 connections, trying to proxy to localhost will fail if resolved to ::1 (IPv6).

Ways to solve it:

Additional IPv6 notes:

Note: There’s a thing called Happy Eyeballs which means connecting to both IPv4 and IPv6 in parallel, which Node.js doesn’t have, but explains why for example curl can connect.

Debugging

Configure the DEBUG environment variable enable debug logging.

See debug project for more options.

DEBUG=http-proxy-middleware* node server.js

$ http-proxy-middleware proxy created +0ms
$ http-proxy-middleware proxying request to target: 'http://www.example.org' +359ms

Working examples

View and play around with working examples.

Recipes

View the recipes for common use cases.

Compatible servers

http-proxy-middleware is compatible with the following servers:

Sample implementations can be found in the server recipes.

Tests

Run the test suite:

# install dependencies
$ yarn

# linting
$ yarn lint
$ yarn lint:fix

# building (compile typescript to js)
$ yarn build

# unit tests
$ yarn test

# code coverage
$ yarn coverage

# check spelling mistakes
$ yarn spellcheck

Changelog

License

The MIT License (MIT)

Copyright (c) 2015-2026 Steven Chim

http-proxy-middleware (chimurai/http-proxy-middleware)

Searching Database…

这是什么?这是一个 Node.js 中间件,只需一行代码就能创建 HTTP 代理,让你把 /api 这类请求转发到另一个主机。它封装了 httpxy 代理引擎,可以接入 connect、express、next.js、hono、fastify 等服务器。
它是独立的服务器,还是我要添加到自己应用里的东西?它是一个中间件库,需要添加到现有的 Node.js 服务器中,而不是独立的代理服务器。
我该如何把它添加到我的服务器中?安装该包,然后至少带上目标主机地址调用 createProxyMiddleware(config),并把返回结果传给 app.use()(如果你使用的服务器框架不同,则使用对应的方法)。
我可以在哪些服务器上使用它?它支持 connect、express、hono、next.js、fastify、browser-sync、lite-server、polka,以及多个 Grunt/Gulp connect 插件。
设置时有没有已知的坑?在 Node.js 17+ 上,代理到 localhost 时可能出现 ECONNREFUSED 错误,原因是 IPv6/IPv4 双栈解析问题(即 'Happy Eyeballs' 问题)。curl 能处理这个问题,但 Node 本身不原生支持。
它支持 WebSocket 代理吗?支持。它既支持内联方式的 WebSocket 代理,也支持通过外部 WebSocket 升级处理的方式,仓库中还附有一个专门的可运行示例。
我可以重写或过滤哪些路径被代理吗?可以。它提供 pathFilter(可以是字符串、数组、glob 或函数)和 pathRewrite(对象或函数)两个选项,用来在请求到达目标之前选择并重写请求路径。
我能在请求和响应经过时查看或修改它们吗?可以。README 中记录了通过插件和 httpxy 事件拦截并修改发出的请求与返回的响应的做法。
代理没有按预期工作时,该怎么调试?设置 DEBUG 环境变量即可开启调试日志,该功能基于标准的 'debug' 包实现。
Creator
chimurai
Size
4.4 MB
Stars
11.1K
Age
11y
Commits · 90 Days