Internal
Public Access
Removed SECURE_CONTENT_TYPE_NOSNIFF and SECURE_BROWSER_XSS_FILTER from Django settings to prevent duplicate headers. These headers are now exclusively managed in Nginx Proxy Manager's Advanced config. This fixes Mozilla Observatory error: "X-Content-Type-Options header cannot be recognized" which was caused by the header being sent twice (once from Django, once from NPM). Security headers now managed in NPM: - Content-Security-Policy - X-Content-Type-Options - X-XSS-Protection - Referrer-Policy - Permissions-Policy X-Frame-Options kept in Django for defense-in-depth (doesn't conflict). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>