3 ms·
Since bouncy is just parsing the http headers and sending along the raw tcp stream How does it deal with a second HTTP requests on one kept-alive connection th
by MartinMond 15y ago
Since bouncy is just parsing the http headers and sending along the raw tcp stream
How does it deal with a second HTTP requests on one kept-alive connection that should be routed to another server?
- substack 15y agoI guess what I was saying there isn't the whole story, since bouncy uses node's http parser directly to handle splitting up keep-alive requests. What I meant was more that bouncy sends data over a tcp stream instead of simply passing the request object through to an http client request.
- MartinMond 15y agoOk, then this is awesome. Also, does it maintain the upstream connections? E.g. do two requests on one kept-alive connection get translated into two separate requests for the upstream server or will the upstream connection also be kept-alive/reused?
- substack 15y agoYou have to roll this yourself right now with a connection pool of stream objects. I'll probably build this out as a separate module.
- MartinMond 15y agoPlease do. I think there is no (open source) proxy out there that supports this.