Opened 8 years ago

Closed 8 years ago

#29357 closed Bug (needsinfo)

Not configuring the `LOGGING` causes to keep the Wsgi server busy

Reported by: Paolo Owned by: nobody
Component: HTTP handling Version: 1.11
Severity: Normal Keywords: LOGGING 404
Cc: Paolo Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Change History (5)

comment:1 by Paolo, 8 years ago

Cc: Paolo added

comment:2 by Tim Graham, 8 years ago

What does it mean that LOGGING isn't configured? I tried LOGGING = {} but couldn't reproduce.

in reply to:  2 comment:3 by Paolo, 8 years ago

Replying to 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.

comment:4 by Tim Graham, 8 years ago

Oh, I guess you'll have to explain the issue a bit more and perhaps provide a sample project that reproduces the problem.

comment:5 by Tim Graham, 8 years ago

Resolution: → needsinfo
Status: new → closed
Note: See TracTickets for help on using tickets.
Back to Top