Bounce your http requests around with bouncy

<p><pre><code> Since bouncy is just parsing the http headers and sending along the raw tcp stream </code></pre> How does it deal with a second HTTP requests on one kept-alive connection that should be routed to another server?

Would be neat to have the ability to forward any TCP connection on port X to host Y port Z.<p>Maybe could even add the ability to peek into the stream to determine which host to forward to based on protocol (think FTP etc.).

It's a cool hack, but if you are going to have a server in front of a web server why not use something like Varnish instead and get caching as well as load balancing.

What's the advantage of using this over tunneling with SSH?

Be awesome if this had a jsgi and/or connect interface to drop in HTTP middleware components for given routes.. is this on your roadmap?

Why would I want to use something like this?