#29357: Not configuring the `LOGGING` causes to keep the Wsgi server busy
-----------------------------------------+-----------------------------
Reporter: Paolo | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
Severity: Normal | Keywords: LOGGING 404
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+-----------------------------
When in a project the **LOGGING** is not configured the requests that
should lead to a **404** just display a **"Not found:"** message instead
of throwing a 404 and keep the Wsgi process busy for an indefinite amount
of time.
--
Ticket URL: <https://code.djangoproject.com/ticket/29357>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.1453f87a183db8dbaf93e55a25b7187b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
