Regression on HTTP Protocol After Updating to Warpgate v0.10.0

[mde-atx]

Hi,
Following the update of Warpgate to version 0.10.0, I have noticed a regression with the HTTP protocol.
Note that this configuration was functional in version 0.9.1

• OS : Ubuntu 20.04.6

• Binary : https://github.com/warp-tech/warpgate/releases/download/v0.10.0/warpgate-v0.10.0-x86_64-linux

• Warpgate Version: v0.10.0

• Warpgate configuration

recordings:
  enable: true
  path: /data/warpgate/recordings
external_host: 
database_url: "mysql://wgdbuser:wgdbpass@127.0.0.1/wgdb"
ssh:
  enable: true
  listen: "0.0.0.0:2222"
  external_port: ~
  keys: /data/warpgate/ssh-keys
  host_key_verification: prompt
  inactivity_timeout: 5m
http:
  enable: true
  listen: "0.0.0.0:8888"
  external_port: ~
  certificate: /data/warpgate/tls.certificate.pem
  key: /data/warpgate/tls.key.pem
  trust_x_forwarded_headers: false
  session_max_age: 30m
  cookie_max_age: 1day
mysql:
  enable: true
  listen: "0.0.0.0:33306"
  external_port: ~
  certificate: /data/warpgate/tls.certificate.pem
  key: /data/warpgate/tls.key.pem
log:
  retention: 7days
  send_to: 
config_provider: database

• WebUI HTTP Target configuration

HTTP Target
Name: gitlab
Target Url: https://gitlab.example.com
Tls mode: Preferred
Verify certificate
bind to domain: empty

Redirect URL : https://warpgate.example.com/?warpgate-target=gitlab

• Debug Log :

06:14:46  INFO Warpgate version=0.10.0
06:14:46  INFO Using config: "/etc/warpgate/config.yaml"
06:14:46  INFO --------------------------------------------
06:14:46  INFO Warpgate is now running.
06:14:46  INFO Accepting SSH connections on 0.0.0.0:2222
06:14:46  INFO Accepting HTTP connections on https://0.0.0.0:8888
06:14:46  INFO Accepting MySQL connections on 0.0.0.0:33306
06:14:46  INFO --------------------------------------------
06:14:46  INFO Listening address=0.0.0.0:2222
06:14:46 DEBUG Database cleaned up, next in 60480s
06:14:46  INFO Listening address=0.0.0.0:8888
06:14:46  INFO Listening address=0.0.0.0:33306
06:14:54  INFO HTTP: Authenticated username=user credentials=password
06:14:54  INFO HTTP: Request method=POST url=/@warpgate/api/auth/login status=201 Created client_ip=127.0.0.1
06:14:54  INFO HTTP: Request method=GET url=/@warpgate/api/info status=200 OK client_ip=127.0.0.1 session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1
06:14:54  INFO HTTP: Request method=GET url=/@warpgate/api/targets?search= status=200 OK client_ip=127.0.0.1 session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1
06:15:05 DEBUG HTTP:: URI: https://gitlab.example.com/?warpgate-target=gitlab session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05  INFO HTTP:: Request method=GET url=/?warpgate-target=gitlab status=302 Found client_ip=127.0.0.1 session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05 DEBUG HTTP:: Rewrote a redirect from "https://gitlab.example.com/users/sign_in" to "/users/sign_in" session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05 DEBUG HTTP:: URI: https://gitlab.example.com/users/sign_in session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05 DEBUG HTTP:: URI: https://gitlab.example.com/favicon.ico session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05  INFO HTTP:: Request method=GET url=/favicon.ico status=301 Moved Permanently client_ip=127.0.0.1 session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05 DEBUG HTTP:: Rewrote a redirect from "https://gitlab.example.com/assets/favicon-72a2cad5025aa931d6ea56c3201d1f18e68a8cd39788c7c80d5b2b82aa5143ef.png" to "/assets/favicon-72a2cad5025aa931d6ea56c3201d1f18e68a8cd39788c7c80d5b2b82aa5143ef.png" session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05 DEBUG HTTP:: URI: https://gitlab.example.com/assets/favicon-72a2cad5025aa931d6ea56c3201d1f18e68a8cd39788c7c80d5b2b82aa5143ef.png session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab
06:15:05  INFO HTTP:: Request method=GET url=/assets/favicon-72a2cad5025aa931d6ea56c3201d1f18e68a8cd39788c7c80d5b2b82aa5143ef.png status=200 OK client_ip=127.0.0.1 session=eb639642-ee2e-40d3-8568-9bab213d28e9 session_username=user client_ip=127.0.0.1 target=gitlab

• Error 502 Bad Gateway

Request failed
Manifest not found