[Django] #29357: Not configuring the `LOGGING` causes to keep the Wsgi server busy
Django
-----------------------------------------+-----------------------------
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.
Django
Reporter: Paolo | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
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
Changes (by Paolo):
* cc: Paolo (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/29357#comment:1>
Django
Reporter: Paolo | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
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
Comment (by Tim Graham):
What does it mean that `LOGGING` isn't configured? I tried `LOGGING = {}`
but couldn't reproduce.
--
Ticket URL: <https://code.djangoproject.com/ticket/29357#comment:2>
Django
Reporter: Paolo | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
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
Comment (by Paolo):
Replying to [comment:2 Tim Graham]:
> What does it mean that `LOGGING` isn't configured? I tried `LOGGING =
{}` but couldn't reproduce.
Just not defining the `LOGGING ` variable at all.
--
Ticket URL: <https://code.djangoproject.com/ticket/29357#comment:3>
Django
Reporter: Paolo | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
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
Comment (by Tim Graham):
Oh, I guess you'll have to explain the issue a bit more and perhaps
provide a sample project that reproduces the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/29357#comment:4>
Django
Reporter: Paolo | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.11
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
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
--
Ticket URL: <https://code.djangoproject.com/ticket/29357#comment:5>