Now that Django 1.10.3 forces ALLOWED_HOSTS on with debug I have a
problem.
The problem is that when I developing I use an ip-address range of
192.168.1.*.
The Ip-adress can change depending on the computer I use.
so I required the ability to add wildcard partly in an hostname.
ie
{{{
ALLOWED_HOSTS = ['192.168.1.*', '.mydomain.com']
}}}
I have seen this solution that doesn't require Django to be changed
however I don't like it as I feel this could be a secuirty issue
http://stackoverflow.com/questions/37031749/django-allowed-hosts-ips-range
I am happy to produce a patch however I will only do this if it's likely
to get submitted
--
Ticket URL: <https://code.djangoproject.com/ticket/27485>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
* component: Uncategorized => HTTP handling
Comment:
I'm sympathetic to the use case, however, before coding I think it'd be
good to raise the idea on the DevelopersMailingList to ensure no one sees
a problem with it or has an alternative.
--
Ticket URL: <https://code.djangoproject.com/ticket/27485#comment:1>
* status: new => closed
* resolution: => wontfix
Comment:
After posting on the group there are way round the problem.
The one I going with is
{{{
from socket import gethostname, gethostbyname
ALLOWED_HOSTS = [ gethostname(), gethostbyname(gethostname()), ]
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27485#comment:2>