Fix CSRF verification by improving Traefik proxy headers
Remove empty X-Forwarded-For header and add X-Scheme header to properly handle HTTPS requests. Add X-Frame-Options for improved security. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -44,8 +44,9 @@ services:
|
||||
- "traefik.http.routers.seafile.middlewares=seafile-headers"
|
||||
- "traefik.http.services.seafile.loadbalancer.server.port=80"
|
||||
- "traefik.http.middlewares.seafile-headers.headers.customrequestheaders.X-Forwarded-Proto=https"
|
||||
- "traefik.http.middlewares.seafile-headers.headers.customrequestheaders.X-Forwarded-For="
|
||||
- "traefik.http.middlewares.seafile-headers.headers.customrequestheaders.X-Forwarded-Host=${SEAFILE_SERVER_HOSTNAME}"
|
||||
- "traefik.http.middlewares.seafile-headers.headers.customrequestheaders.X-Scheme=https"
|
||||
- "traefik.http.middlewares.seafile-headers.headers.customresponseheaders.X-Frame-Options=SAMEORIGIN"
|
||||
depends_on:
|
||||
- db
|
||||
- memcached
|
||||
|
||||
Reference in New Issue
Block a user