Wired the trailing-slash redirect into the App router in the Website service target.

2026-08-24 17:37:46 +02:00
parent 5996a78ff3
commit c0f56a4897
1 changed files with 5 additions and 0 deletions
@@ -138,6 +138,11 @@ Redirecting collapses the `http://` and `https://` copies of every page onto one
 `docker-compose.yml` enables it for production; `docker-compose.override.yml` pins it off for local development.
 Trailing slashes are canonicalized separately and unconditionally, with no configuration key: the router matches `/mr-rock` and `/mr-rock/` alike, so
 every `GET`/`HEAD` whose path ends in a slash is answered with a `301` to the form without one (`//` collapses to `/`; `/` is left alone). The
 `Location` is relative, so it keeps the request's own scheme and host. Other methods pass through, since a client may repeat a redirected `POST` as a
 `GET` and drop the body.
 ### Logging
 | Config key | Environment variable | Default | Description |
 | --- | --- | --- | --- |