Hi all - I recently upgraded to Node-Red 3.1 (docker) and I'm having a weird issue with the "http request" nodes. I rolled back to 3.0 to confirm that it was the upgrade that caused the problem.
It seems like in 3.1 they've added the ability to set your own headers in the http request node. When I upgrade, I get a ERR_TLS_CERT_ALTNAME_INVALID error, stating that my hostname (localhost) doesn't match the hostname alts in my certificate.
My node-red is behind SWAG / Nginx, so I think I need to set a header. Something like X-Forwarded-For or something to indicate that its through a proxy. I tried setting "Enable secure (SSL/TLS) connection" and then making sure that "Verify server certificate" was unchecked. This resulted in the repose returning my "Welcome to SWAG" page from nginx. Also tried setting msg.rejectUnauthorized to false, same result.
Once I switched back to 3.0, the TLS connection was back to normal without errors, and was returning expected results. So I think whats happening is that the hostname for 3.1 is being defaulted to localhost, and when it tries to verify the requesting server using TLS, it doesn't match. So it fails.
Anyone know of the environment variable to set the hostname? I've tried setting VIRTUAL_HOST, and also just dnsname and hostname at the service level of my docker-compose, nothing seemed to work. That, or does anyone know what header I should be setting for these http request nodes? Thanks!