tlamatini-allowed-hosts-tighten

Removing the wildcard from Django ALLOWED_HOSTS prevents host header attacks by ensuring the web app only accepts requests for explicitly trusted domains. Replacing the permissive ['*'] default with a custom whitelist reduces exposure to malicious HTTP requests.

To safely replace ALLOWED_HOSTS, back up settings.py as settings.py.bak before modifying. The skill rewrites ALLOWED_HOSTS to your provided whitelist and returns the file paths and changed status, ensuring a rollback path if the provided hosts are invalid.

Yes, you can restore your original Django settings.py from the backup file. The skill automatically creates settings.py.bak before applying changes, allowing rollback by restoring the backup if the provided hosts are invalid.

Tightening ALLOWED_HOSTS requires no external dependencies. The skill operates directly on the filesystem to locate, back up, and rewrite Django's settings.py, enforcing read/write permissions to safely apply the security whitelist.

The best way to secure Django ALLOWED_HOSTS for production is replacing the wildcard entry with a specific domain whitelist. This enforces strict host validation, backs up the original configuration, and mitigates host header attack vectors.

When ALLOWED_HOSTS is rewritten, the skill reports the outputs settings_path, backup_path, and changed. It locates the setting in settings.py, creates a backup, and returns these paths along with the change status for verification.