What is the point of the 'secure' option

[Marc477]

What is the point of the 'secure' if the module only works (in https) when it is set to false ??

In an https.request, when we set rejectUnauthorized to true we also have to set the ca (certificate authority file), otherwise the certificate will fail validating. But there is no way to set https.request ca option in http-proxy.

[Marc477]

Fixed it by adding:

if(options.ca){
outgoing.ca = options.ca;
}

in common.js inside function common.setupOutgoing

Now it is working, but this should really be added to this project

[jcrugzz]

@Marc477 pull-requests very much welcome

[Marc477]

I just found out that if a put all the certificate chain in my .crt file, I don't need to add it as ca parameter to https request ! But self-signed certificates are still a mystery for me since i always get the error: UNABLE_TO_VERIFY_LEAF_SIGNATURE, even after adding it to ca param

[Marc477]

Ok we need to add CA to server too, so we need to add CA option to http-proxy for self-signed certificates

[predhme]

I created a pull request here: #1042

Forgive me as I am unfamiliar with the projects setup, but this change I can assert fixes the problem that @Marc477 originally reported. I was encountering the same issue when using HTTPS to HTTPS with secure: true.