#27485: ALLOWED_HOSTS ip-range / wildcard
-----------------------------------------+-------------------------------
               Reporter:  Tom Turner     |          Owner:  nobody
                   Type:  New feature    |         Status:  new
              Component:  Uncategorized  |        Version:  1.10
               Severity:  Normal         |       Keywords:  ALLOWED_HOSTS
           Triage Stage:  Unreviewed     |      Has patch:  0
    Needs documentation:  0              |    Needs tests:  0
Patch needs improvement:  0              |  Easy pickings:  0
                  UI/UX:  0              |
-----------------------------------------+-------------------------------
 Hi

 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.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.9b5bba3c14e2afef339900da03fde3d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to