Files
tfm_ainventory/Caddyfile.standalone
Daniel Bedeleanu 0881b0ecee fix(6): resolve static asset serving and proxy header issues
Fixed issues:
1. Caddy not forwarding X-Forwarded headers to Next.js
   - Added X-Forwarded-For, X-Forwarded-Proto, X-Forwarded-Host
2. Removed X-Content-Type-Options: nosniff (blocks static assets)
3. Copy static files to standalone build directory
   - Next.js standalone requires files in .next/standalone/.next/static/
4. Made script auto-copy static files after build

Result:
  ✓ CSS/JS loading with correct MIME types (text/css, text/javascript)
  ✓ Frontend fully rendering via HTTPS
  ✓ All static assets cached and served correctly
  ✓ Tested working via IP address (192.168.84.131:8919)
2026-04-22 19:34:32 +03:00

50 lines
1.1 KiB
Caddyfile

# TFM aInventory - Standalone Caddy Configuration
# Self-signed SSL/TLS reverse proxy for any IP/hostname
{
admin off
local_certs
skip_install_trust
on_demand_tls {
ask http://localhost:8916/
}
}
# Dynamic HTTPS Frontend (port 8919) - Matches ANY IP or hostname
https://:8919 {
tls internal {
on_demand
}
reverse_proxy localhost:8917 {
header_up X-Forwarded-For {remote_host}
header_up X-Forwarded-Proto https
header_up X-Forwarded-Host {host}
}
header {
Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
X-XSS-Protection "1; mode=block"
X-Frame-Options "SAMEORIGIN"
Referrer-Policy "strict-origin-when-cross-origin"
}
}
# Dynamic HTTPS Backend (port 8918) - Matches ANY IP or hostname
https://:8918 {
tls internal {
on_demand
}
reverse_proxy localhost:8916 {
header_up X-Forwarded-For {remote_host}
header_up X-Forwarded-Proto https
header_up X-Forwarded-Host {host}
}
header {
Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
}
}