website/docs: Correct the forward authentication configuration template for Caddy (#11012)
Correct the forward authentication configuration template for Caddy The directives were not executed in the given order, but instead, using the implicit sequence defined in https://caddyserver.com/docs/caddyfile/directives#directive-order. Surrounding the directives with route {} fixes this. Signed-off-by: Andreas <43118918+eulores@users.noreply.github.com>
This commit is contained in:
@ -2,6 +2,8 @@ Use the following configuration:
|
|||||||
|
|
||||||
```
|
```
|
||||||
app.company {
|
app.company {
|
||||||
|
# directive execution order is only as stated if enclosed with route.
|
||||||
|
route {
|
||||||
# always forward outpost path to actual outpost
|
# always forward outpost path to actual outpost
|
||||||
reverse_proxy /outpost.goauthentik.io/* http://outpost.company:9000
|
reverse_proxy /outpost.goauthentik.io/* http://outpost.company:9000
|
||||||
|
|
||||||
@ -19,6 +21,7 @@ app.company {
|
|||||||
# actual site configuration below, for example
|
# actual site configuration below, for example
|
||||||
reverse_proxy localhost:1234
|
reverse_proxy localhost:1234
|
||||||
}
|
}
|
||||||
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
If you're trying to proxy to an upstream over HTTPS, you need to set the `Host` header to the value they expect for it to work correctly.
|
If you're trying to proxy to an upstream over HTTPS, you need to set the `Host` header to the value they expect for it to work correctly.
|
||||||
|
Reference in New Issue
Block a user