Ken "Elf" Mathieu Sternberg 411bb51cc6 Fix issue where front-end is HTTPS, back-end is HTTP, and server issues a redirect. ...

This handles the case where a back-end web application such as Django or
Rails issues a redirect and automatically decorates the URL with the
protocol with which it was addressed.  If the back-ends are internal and
HTTP-only, then they'll issue a URL with 'http://' as the protocol.
This must be fixed before leaving the proxy.

This also handles the (unusual) case where a back-end speaks only
https://, but the user is deploying node-http-proxy to make that service
available to non-SSL capable browsers.  Works only with 301 and 302
codes.

2011-11-29 10:10:16 -08:00

..

node-http-proxy

Fix issue where front-end is HTTPS, back-end is HTTP, and server issues a redirect.

2011-11-29 10:10:16 -08:00

node-http-proxy.js

don't add upgrade handler if a custom handler is passed in

2011-11-16 16:40:51 -08:00