davidmonterocrespo24 924e1cb02a fix(nginx): use relative redirects so trailing-slash 301s preserve HTTPS ... Browsers were reporting: Unsafe attempt to load URL http://velxio.dev/examples/ from frame with URL https://velxio.dev/examples. Repro: curl -I https://velxio.dev/examples → 301 Location: http://velxio.dev/examples/ ← protocol downgraded Why: docker/nginx.conf has the container listening on `:80` only — TLS is terminated by the host nginx in front of it (which then proxies to http://127.0.0.1:3080). When nginx generates a trailing-slash 301 it uses the listening protocol (http) for the absolute Location header, not the X-Forwarded-Proto. The browser correctly blocks the redirect. Fix: `absolute_redirect off;` makes nginx emit relative Location headers (`Location: /examples/`), so the browser resolves them against the original request URL and HTTPS is preserved end-to-end. After fix: curl -I https://velxio.dev/examples → 301 Location: /examples/ Goes in the same branch as the BMP280 ninja-timeout fix because both are deploy-blocking and small. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-09 04:56:35 +02:00
..
entrypoint.sh	refactor: rename deploy/ → docker/ (container build, not host deploy)	2026-05-04 00:05:55 -03:00
nginx.conf	fix(nginx): use relative redirects so trailing-slash 301s preserve HTTPS	2026-05-09 04:56:35 +02:00