Skip to content

Latest commit

 

History

History
239 lines (171 loc) · 7.5 KB

README.md

File metadata and controls

239 lines (171 loc) · 7.5 KB

fastify-reply-from

Greenkeeper badge

Build Status NPM version

fastify plugin to forward the current http request to another server. HTTP2 to HTTP is supported too.

Install

npm i fastify-reply-from

Usage

The following example set up two fastify servers and forward the request from one to the other.

'use strict'

const Fastify = require('fastify')

const target = Fastify({
  logger: true
})

target.get('/', (request, reply) => {
  reply.send('hello world')
})

const proxy = Fastify({
  logger: true
})

proxy.register(require('fastify-reply-from'), {
  base: 'http://localhost:3001/'
})

proxy.get('/', (request, reply) => {
  reply.from('/')
})

target.listen(3001, (err) => {
  if (err) {
    throw err
  }

  proxy.listen(3000, (err) => {
    if (err) {
      throw err
    }
  })
})

API

Plugin options

base

Set the base URL for all the forwarded requests. Will be required if http2 is set to true Note that every path will be discarded.

http

By default, Node's http.request will be used if you don't enable http2 or undici. To customize the request, you can pass in agentOptions and requestOptions. To illustrate:

proxy.register(require('fastify-reply-from'), {
  base: 'http://localhost:3001/',
  http: {
    agentOptions: { // pass in any options from https://nodejs.org/api/http.html#http_new_agent_options
      keepAliveMsecs: 10 * 60 * 1000
    },
    requestOptions: { // pass in any options from https://nodejs.org/api/http.html#http_http_request_options_callback
      timeout: 5000 // timeout in msecs, defaults to 10000 (10 seconds)
    }
  }
})

http2

You can either set http2 to true or set the settings object to connect to a HTTP/2 server. The http2 settings object has the shape of:

proxy.register(require('fastify-reply-from'), {
  base: 'http://localhost:3001/',
  http2: {
    sessionTimeout: 10000, // HTTP/2 session timeout in msecs, defaults to 60000 (1 minute)
    requestTimeout: 5000, // HTTP/2 request timeout in msecs, defaults to 10000 (10 seconds)
    sessionOptions: { // HTTP/2 session connect options, pass in any options from https://nodejs.org/api/http2.html#http2_http2_connect_authority_options_listener
      rejectUnauthorized: true
    },
    requestTimeout: { // HTTP/2 request options, pass in any options from https://nodejs.org/api/http2.html#http2_clienthttp2session_request_headers_options
      endStream: true
    }
  }
})

undici

Set to true to use undici instead of require('http'). Enabling this flag should guarantee 20-50% more throughput.

This flag could controls the settings of the undici client, like so:

proxy.register(require('fastify-reply-from'), {
  base: 'http://localhost:3001/',
  undici: {
    connections: 100,
    pipelining: 10
  }
})

cacheURLs

The number of parsed URLs that will be cached. Default: 100.

keepAliveMsecs

(Deprecated) Defaults to 1 minute (60000), passed down to http.Agent and https.Agent instances. Prefer to use http.agentOptions instead.

maxSockets

(Deprecated) Defaults to 2048 sockets, passed down to http.Agent and https.Agent instances. Prefer to use http.agentOptions instead.

maxFreeSockets

(Deprecated) Defaults to 2048 free sockets, passed down to http.Agent and https.Agent instances. Prefer to use http.agentOptions instead.

rejectUnauthorized

(Deprecated) Defaults to false, passed down to https.Agent instances. This needs to be set to false to reply from https servers with self-signed certificates. Prefer to use http.requestOptions or http2.sessionOptions instead.

sessionTimeout

(Deprecated) The timeout value after which the HTTP2 client session is destroyed if there is no activity. Defaults to 1 minute (60000). Prefer to use http2.sessionTimeout instead.


reply.from(source, [opts])

The plugin decores the Reply instance with a from method, which will reply to the original request from the desired source. The options allows to override any part of the request or response being sent or received to/from the source.

onResponse(request, reply, res)

Called when an http response is received from the source. The default behavior is reply.send(res), which will be disabled if the option is specified.

rewriteHeaders(headers)

Called to rewrite the headers of the response, before them being copied over to the outer response. It must return the new headers object.

rewriteRequestHeaders(originalReq, headers)

Called to rewrite the headers of the request, before them being sent to the other server. It must return the new headers object.

queryString

Replaces the original querystring of the request with what is specified. This will get passed to querystring.stringify.

body

Replaces the original request body with what is specified. Unless [contentType][contentType] is specified, the content will be passed through JSON.stringify(). Setting this option will not verify if the http method allows for a body.

contentType

Override the 'Content-Type' header of the forwarded request, if we are already overriding the [body][body].

logProxyError(log, err)

Override the default logging of proxy errors, allowing the changing of format or addition of information. You may also disable by setting to false.

logProxyRequest(log, source, requestConfig)

Override the default logging of proxy requests, allowing the changing of format or addition of information. You may also disable by setting to false.

logProxyResponse(log, res)

Override the default logging of proxy responses, allowing the changing of format or addition of information. You may also disable by setting to false.

HTTP & HTTP2 timeouts

This library has:

  • timeout for http set by default. The default value is 10 seconds (10000).
  • requestTimeout & sessionTimeout for http2 set by default.
    • The default value for requestTimeout is 10 seconds (10000).
    • The default value for sessionTimeout is 60 seconds (60000).

When a timeout happens, 504 Gateway Timeout will be returned to the client.

TODO

  • support overriding the body with a stream
  • forward the request id to the other peer might require some refacotring because we have to make the req.id unique (see hyperid).
  • Support origin HTTP2 push
  • benchmarks

License

MIT