#36514: Improve ALLOWED_HOSTS error message: show both values
------------------------------------+--------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: New feature | Status: closed
Component: HTTP handling | Version: 5.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Comment (by Klaas van Schelven):
> In real world deployments, it's common to include internal hostnames,
IP addresses, or ephemeral domains that are not externally visible, for
example in environments where SSL termination and routing are handled
separately from the Django app itself.
That's a fair point for the "this isn't a good fit for Django" case.
I'd argue that the following point remains: for the most common
misconfiguration at the proxy level, Django now explicitly suggests to add
localhost to ALLOWED_HOSTS. This is generally exactly the opposite of what
you want. Could we say _that_ is a bug?
--
Ticket URL: <https://code.djangoproject.com/ticket/36514#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701982e35e6dd-071218ad-741d-41b2-bbad-8286e1dd0098-000000%40eu-central-1.amazonses.com.
