### fix: verbessere CORS-Handling im Caddy-Proxy
Build and Publish Docker Images / build-and-push (., backend/services/mail/Dockerfile, mail-service, mail-service) (push) Successful in 5m47s
Build and Publish Docker Images / build-and-push (., config/docker/caddy/web-app/Dockerfile, web-app, web-app) (push) Successful in 3m55s

- **Caddyfile:** Hinzufügen des `defer`-Flags zur korrekten Verarbeitung von CORS-Headern.
- **UI:** Aktualisierung des Versionsmarkers auf `v2026-04-23.22 - CADDY DEFER CORS FIX`.
- **Docs:** Ergänzung der Analyse und Lösung für Version 22.
This commit is contained in:
2026-04-23 13:25:02 +02:00
parent 71aea3f41d
commit 03fa74abba
3 changed files with 14 additions and 14 deletions
+6 -13
View File
@@ -17,27 +17,20 @@
encode gzip zstd
# Reverse Proxy: Plan-B leitet nur /api/mail an den Mail-Service weiter (kein API-Gateway nötig)
# Reverse Proxy: Plan-B leitet nur /api/mail an den Mail-Service weiter
handle /api/mail/* {
# CORS Handshake direkt im Proxy abfangen (Plan-B radikal)
@options method OPTIONS
header @options {
Access-Control-Allow-Origin "https://app.mo-code.at"
Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
Access-Control-Allow-Headers "*"
Access-Control-Allow-Credentials "true"
Access-Control-Max-Age "3600"
}
respond @options 204
# CORS Header auch für die eigentlichen Antworten (GET/POST) setzen
header {
Access-Control-Allow-Origin "https://app.mo-code.at"
Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
Access-Control-Allow-Headers "*"
Access-Control-Allow-Credentials "true"
Access-Control-Max-Age "3600"
defer
}
@options method OPTIONS
respond @options 204
reverse_proxy mail-service:8085
}