Files
Liosha84andClaude Opus 5.5 7f2c1ec282 fix: trust proxy forwarded headers so login works behind Caddy
Behind Jambotron's Caddy the app saw http while the browser used https,
so same-domain requests looked cross-origin and @CrossOrigin answered
403 on /api/auth/signin. server.forward-headers-strategy=framework makes
the app use X-Forwarded-Proto/Host; app.origin can be set via APP_ORIGIN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 22:29:31 +02:00

36 lines
1.2 KiB
Nginx Configuration File

# Схема исходного запроса: за Caddy (https) — из его X-Forwarded-Proto, иначе своя
map $http_x_forwarded_proto $forwarded_proto {
default $http_x_forwarded_proto;
"" $scheme;
}
server {
listen 80;
server_name _;
root /usr/share/nginx/html;
index index.html;
# UI ходит в API по относительному пути /api — проксируем на бэкенд,
# так браузер видит один origin и JWT-cookie работает без CORS
location /api/ {
proxy_pass http://backend:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $forwarded_proto;
}
# Маршруты Angular (/admin, /tutorials/1 ...) отдаём через index.html
location / {
try_files $uri $uri/ /index.html;
}
# Файлы сборки с хешем в имени можно кэшировать надолго
location ~* \.(?:js|css|ico|png|svg|woff2?)$ {
try_files $uri =404;
expires 1y;
add_header Cache-Control "public, immutable";
}
}