Also wondering if it is a bad idea to use http-proxy instead of http-reverse-proxy because it supports SSL?

I'd rather do this in a way that doesn't break backwards compatibility with all users. How about adding a new constructors WPRProxyDestSecure instead?

That sounds super reasonable; solves the rawProxyTo issue as well!

I'll submit a follow-up commit tomorrow.
On Nov 18, 2015 00:17, "Michael Snoyman" notifications@github.com wrote:

I'd rather do this in a way that doesn't break backwards compatibility
with all users. How about adding a new constructors WPRProxyDestSecure
instead?

—
Reply to this email directly or view it on GitHub
#15 (comment)
.

Having both WPRProxyDestSecure and WPRModifiedRequestSecure feels a tiny bit icky, but I'm not seeing a better approach.

Thanks!