Support Virtual Host for HTTP Proxy Module

[magkani]

HTTP Proxy Module
I would like to suggest to add in few lines of code to preserve the host name and forward it to the application to support virtual host.

Currently the host is being set to blank.

BounceBack/internal/proxy/http/proxy.go

Line 152 in bc9dc7a

r.Host = ""

Below are the suggested improvement, pull request created #21.

origHost := r.Host
if origHost == "" {
	origHost = r.Header.Get("Host")
}
r.Host = origHost

[D00Movenok]

Hello! Thank you for your feauture request.

I've verified the following:

1. The host header is automatically changed to the host and port from the "target" field in the configuration.
2. The SNI in TLS Hello is also set to the "target" host from the configuration.

And all of this works without your patch.

What am I missing that isn't working for you? I don't understand what your feauture request does.

[magkani]

Hi, thanks for your clarification. I am not sure if I miss out any parts of the configuration, I would like would like to share the scenarios that I have facing.

I have multiple applications hosted within the server with different domain name (e.g. vhost or server blocks), for instance app1.example.com, app2.example.com and app3.example.com. From external they are all access through https (port 443).

Below are my configurations

proxies:
  - name: my_https_proxy
    type: http
    listen: 0.0.0.0:443
    target: https://127.0.0.1:8443
    timeout: 10s
    tls:
      - cert: /etc/letsencrypt/live/app1.example.com/fullchain.pem
        key: /etc/letsencrypt/live/app1.example.com/privkey.pem
        domains:
          - "app1.example.com"
      - cert: /etc/letsencrypt/live/app2.example.com/fullchain.pem
        key: /etc/letsencrypt/live/app2.example.com/privkey.pem
        domains:
          - "app2.example.com"
      - cert: /etc/letsencrypt/live/app3.example.com/fullchain.pem
        key: /etc/letsencrypt/live/app3.example.com/privkey.pem
        domains:
          - "app3.example.com"
      

Issue observed
When I am trying to access the app3.example.com, the proxy did not point to the correct app, it went into the app1.example.com instead.