Reverse proxy question

[graphixillusion (Gabe)]

I already tried without transparent and without websocket, still the same result. Btw, the target of the reverse proxy is not something like website-b.example.com: in the browser the address will always stays at example.com.

@Whitestrake

Caddy’s proxy does NOT issue a redirect.

Yep, right: the address will not change to the WEBSITE-B’s address. I used the wrong terminology.

[Whitestrake (Matthew Fay)]

I tried to replicate the problem with the simplest possible configuration, but it worked exactly as expected.

~/Projects/test
➜ mkdir website1 website2

~/Projects/test
➜ echo "I'm website 1!" > website1/index.txt

~/Projects/test
➜ echo "I'm website 2!" > website2/index.txt

~/Projects/test
➜ cat Caddyfile
:8080 {
  proxy / localhost:8081
  proxy /rb localhost:8082 {
    without /rb
  }
}

:8081 {
  root website1
}

:8082 {
  root website2
}

~/Projects/test
➜ caddy -version
v1.0.4

~/Projects/test
➜ curl localhost:8080
I'm website 1!

~/Projects/test
➜ curl localhost:8080/rb
I'm website 2!

[graphixillusion (Gabe)]

@Whitestrake

I tried to replicate the problem with the simplest possible configuration, but it worked exactly as expected.

This is very strange indeed. I replicate your simple example and it works. But when i try with this Caddyfile, it doesn’t…

example.com:443 {
  header / Strict-Transport-Security "max-age=31536000"
  proxy / https://INTERNAL-IP-A {
    transparent
    websocket
    insecure_skip_verify
    }
  proxy /rp INTERNAL-IP-B {
    without /rp 
    }
}

Maybe external webservers manage those type of requests in a different way…