mirror of
https://github.com/django/django.git
synced 2025-10-31 09:41:08 +00:00
Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.
This commit is contained in:
committed by
Mariusz Felisiak
parent
acde917456
commit
1024b5e74a
@@ -17,10 +17,10 @@ Host header poisoning
|
||||
Some parts of Django -- independent of end-user-written applications -- make
|
||||
use of full URLs, including domain name, which are generated from the HTTP Host
|
||||
header. Django's documentation has for some time contained notes advising users
|
||||
on how to configure Web servers to ensure that only valid Host headers can reach
|
||||
on how to configure web servers to ensure that only valid Host headers can reach
|
||||
the Django application. However, it has been reported to us that even with the
|
||||
recommended Web server configurations there are still techniques available for
|
||||
tricking many common Web servers into supplying the application with an
|
||||
recommended web server configurations there are still techniques available for
|
||||
tricking many common web servers into supplying the application with an
|
||||
incorrect and possibly malicious Host header.
|
||||
|
||||
For this reason, Django 1.4.4 adds a new setting, ``ALLOWED_HOSTS``, containing
|
||||
|
||||
Reference in New Issue
Block a user