HTTP target not working properly because HTTP host header is not being set
cougz opened this issue · comments
TimSt commented
Hi,
I am testing HTTP targets of warpgate and noticed that the proxy of warpgate does not set HTTP host header when forwarding TLS connections.
Now, when using nginx, I would simply add the header to the config (proxy_set_header Host $host;)
But for warpgate, as far as I know, there is no option to configure this.
Unfortunately, because of this, the HTTP target (Jetty) I am trying to access does not display web content properly.
Is there any way to fix this issue?
Thanks!