dominictarr/connect-restreamer

#connect-restreamer

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.

usage

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

require('http-proxy').createServer(
  //refactor the body parser and re-streamer into a separate package
  bodyParser(),
  //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.
  require('connect-restreamer')(),
  function (req,res, proxy) {
    //custom proxy logic
    //... see https://github.com/nodejitsu/node-http-proxy
  }
).listen(80)

customization

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
}

require('connect-restreamer')(options)

connect-restreamer's Issues

write after end

Getting this error

Error: write after end
   at ClientRequest.OutgoingMessage.write (_http_outgoing.js:413:15)
   at IncomingMessage.ondata (_stream_readable.js:540:20)
   at IncomingMessage.emit (events.js:107:17)
   at C:\...\node_modules\connect-restreamer\index.js:18:13
   at process._tickCallback (node.js:355:11)

Using this simple code: gist. Getting the error only on POST requests, probably when something with body parsing is involved.

Is there a limit on how much data is streamed before a connection closes?

I take an incoming request, change its body, restream it and proxy it onwards. So I expect to receive the entire body at the server to which the request was proxied.

https://gist.github.com/pulkitsinghal/5ab774376338ae37b9a6

But instead of {"a":{"b":{"c":[]}}} I receive {"a":{"b":{"c and an error stating Error: socket hang up ... so do I need to configure connect-restreamer in some way to get all the data re-streamed?

Apache License

Hi, we are trying to use connect-restreamer for our company and our legal department only clears libraries with Apache licenses. I was wondering if you could add the Apache License to connect-restreamer? Thanks.

License file?

What license is this repo covered by?

I see many of your other repos are MIT licensed, happy to make a pull request for this one if that is helpful.

Thanks!