I'm trying to build a proxy server using node.js that abides by all the RFC-2616 rules for general proxy servers, e.g. inserting Via: headers (sec 14.45) and deleting hop-by-hop headers such as Connection: and the headers mentioned in Connection: (sec. 14.10). You know, the kind of proxy server you can configure your browser to use directly, e.g. as an egress proxy on your intranet, and all your normal HTTP and HTTPS browsing will just continue to work through it.
Unlike a reverse proxy installed on the server side, it can't be entirely transparent, it has to modify certain headers as they go by, according to the very specific proxy rules spelled out in RFC-2616, or it will screw things up for some kinds of requests. And of course it has to correctly handle every conceivable kind of request, to any server anywhere, not just those expected at a particular site. It looks as if nodejitsu http-proxy doesn't quite do this for you. I've also found one thing in the node.js source itself that seems to be an obstacle to doing it properly (in _addHeaderLine). It kind of looks as if no one has been using node.js as the kind of proxy server that you can configure your browser to use all day? Does anyone know of anyone who has been there before me? I don't want to re-invent the wheel -- if someone out there already has done this already, or has any experience using node.js as a proxy server to which browsers connect directly, I'd really like to talk to them. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
