Keith SmithandClaude Sonnet 4.5 de57befe3a Restore Django security headers for defense-in-depth ...

Re-added SECURE_CONTENT_TYPE_NOSNIFF and SECURE_BROWSER_XSS_FILTER
to Django settings. These don't conflict with NPM's "Block Common
Exploits" feature - they provide defense-in-depth by ensuring headers
are set even if the request bypasses NPM.

Security header strategy:
- NPM (primary): CSP, HSTS, Referrer-Policy, Permissions-Policy,
  X-Content-Type-Options, X-XSS-Protection via "Block Common Exploits"
- Django (backup): X-Frame-Options, X-Content-Type-Options,
  X-XSS-Protection for defense-in-depth

This follows security best practice of setting headers at multiple
layers rather than relying on a single point of control.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2025-12-26 18:17:34 -07:00

..

settings

Restore Django security headers for defense-in-depth

2025-12-26 18:17:34 -07:00

__init__.py

Initial commit: KeepItGoing task management server

2025-12-18 17:41:29 -07:00

asgi.py

Initial commit: KeepItGoing task management server

2025-12-18 17:41:29 -07:00

celery.py

Fix Critical Security Issue: Replace print() with proper logging

2025-12-22 22:34:57 -07:00

urls.py

Add API root endpoint at /api/

2025-12-26 17:24:16 -07:00

views.py

Add API root endpoint at /api/

2025-12-26 17:24:16 -07:00

wsgi.py

Initial commit: KeepItGoing task management server

2025-12-18 17:41:29 -07:00