The current wrapping of http-proxy doesn't expose the 'secure' option it assumes that https = true is the same as secure = true.
secure = true in http-proxy determines if the SSL checks should occur not the transport. This exposes the option to users, while keeping the previous behavior the same.
ruiaraujo
commented
9 years ago
The current wrapping of http-proxy doesn't expose the 'secure' option it assumes that https = true is the same as secure = true. secure = true in http-proxy determines if the SSL checks should occur not the transport. This exposes the option to users, while keeping the previous behavior the same.