Opened 9 years ago

Closed 9 years ago

Last modified 2 years ago

#2494 closed enhancement (fixed)

Django internal server does too much reverse dns

Reported by: tpievila@… Owned by: adrian
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: UI/UX:

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.

Change History (3)

comment:1 Changed 9 years ago by adrian

  • Resolution set to fixed
  • Status changed from new to closed

(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

comment:2 Changed 2 years ago by Claude Paroz <claude@…>

In 3e98d98b69e67f2f72055e4b3204d0486eaeff50:

Prevented host resolution when running dev server

Refs #19075, #2494.
Thanks Karen Tracey for spotting the issue.

comment:3 Changed 2 years ago by Claude Paroz <claude@…>

In e51a9c0c948855ed8fe7e1a694e17727af604926:

[1.5.x] Prevented host resolution when running dev server

Refs #19075, #2494.
Thanks Karen Tracey for spotting the issue.

Backport of 3e98d98b6 from master.

Note: See TracTickets for help on using tickets.
Back to Top