Django

Code

Ticket #2494 (closed: fixed)

Opened 2 years ago

Last modified 2 years ago

Django internal server does too much reverse dns

Reported by: tpievila@cc.hut.fi Assigned to: adrian
Milestone: Component: Core framework
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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.

Attachments

Change History

08/07/06 09:41:57 changed by adrian

  • status changed from new to closed.
  • resolution set to fixed.

(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

Add/Change #2494 (Django internal server does too much reverse dns)




Change Properties
Action