#2494 closed enhancement (fixed)
Django internal server does too much reverse dns
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Core (Other) | Version: | |
| Severity: | minor | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When using django internal server from outside lan, there is considerable slowdown for every GET request. This means that if the page links to many stylesheets or JavaScripts, the loading time may exceed tens of seconds.
The problem has been tracked to the internal server doing a reverse dns query for every GET request, adding the client's ip to /etc/hosts circumvents this problem. Also using Apache will work, but in development phase that is not nice at all compared to the dev server that automaticaly notices changes in code and reloads with validations.
Note:
See TracTickets
for help on using tickets.
(In [3530]) Fixed #2494 -- Django development server no longer does reverse DNS. As a side effect, the server no longer sets the REMOVE_HOST environment variable