Removed last nodejitsu reference

* declare app variable to house middleware

* remove deprecated connect.createServer() function call

* specify middleware with app.use() and pass app middleware to an http
server

There were errors in the examples highlighted, check issue #969

With more than 1 proxy the original host was lost, now it will be passed down the proxy chain

Updates options documentation for location rewrite to include 201 responses. See #1024

Currently published version includes .nyc_output and coverage

* Add renovate.json

* [dist] Configure renovate more.

[examples] Restream body before proxying, support for Content-Type of application/x-www-form-urlencoded (#1264)

[test] add test for selfHandleRequest and remove modifyResponse as selfHandleRequest is the only way that functionality works

object.keys in web-incoming.js results in a non-deterministic ordering of keys, which means that in web-outgoing writeHead might be called before setHeader, which throws an error

This PR tries to fix "Can't set headers after they are sent" errors.
That are a lot of situations where this error can occurs. In my case, it is happening because I have others middlewares (in an expressjs application that tries to proxy requests). Some of those middlewares (like [passportjs](http://passportjs.org/), or [cors](https://www.npmjs.com/package/cors)) can run ```res.end()``` and when the proxy receive a response, it is already finished.
So, it is necessary to test if we can write on the user response when the proxy response is ready.
I think it could also fix #930, #1168, #908

When the server do not accept the upgrade request for websockets the
server's response was previously not included and sent back. Now the
proxy will include the response in these cases. Fixes #890.