re-stream a parsed body so that it can be proxied.
Last updated 5 years ago by ngourley .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install connect-restreamer 
SYNC missed versions from official npm registry.


connect's bodyParser has a problem when using it with a proxy. It gobbles up all the body events, so that the proxy doesn't see anything!

connect-restreamer comes to the rescue by re-emitting the body to the proxy.

it has defaults that make it suitable for use with connect's bodyParser but can be customized.


just include connect-restreamer in you're middleware chain after the bodyParser

var bodyParser = require('connect/lib/middleware/bodyParser')
  , restreamer = require('connect-restreamer')

//don't worry about incoming contont type
//bodyParser.parse[''] = JSON.parse

  //refactor the body parser and re-streamer into a separate package
  //body parser absorbs the data and end events before passing control to the next
  // middleware. if we want to proxy it, we'll need to re-emit these events after 
  //passing control to the middleware.
  function (req,res, proxy) {
    //custom proxy logic
    //... see


restreamer takes 3 options:

var options = {
  modify: function(body) {
    //a function that may modify the buffered property
    return body
  property: 'body', //name of the buffered property
  stringify:JSON.stringify //function to turn the buffered object back into a string


Current Tags

  • 1.0.3                                ...           latest (5 years ago)

4 Versions

  • 1.0.3                                ...           5 years ago
  • 1.0.2                                ...           5 years ago
  • 1.0.1                                ...           6 years ago
  • 1.0.0                                ...           9 years ago
Maintainers (1)
Today 2
This Week 25
This Month 11
Last Day 9
Last Week 29
Last Month 142
Dependencies (0)
Dev Dependencies (0)

Copyright 2014 - 2016 © |