#14800: Development server should NOT elide favicon from the logs
-------------------------------------+-------------------------------------
Reporter: RoySmith | Owner:
Type: New feature | Status: new
Component: Core (Management | Version: 1.2
commands) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: logging | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by RoySmith):
OK, I did some research. The original ticket which led to this behavior
was #161. I don't understand the full motivation behind this, but I'm
assuming it was along the lines of "these are just static files, no need
to clutter up the log with them". I disagree with that philosophy, but
let's assume for the moment it's a valid concept. In my case, /favicon.png
matched a pattern in my urls file and got dispatched to a view. Surely the
original author of the feature never intended to elide from the logs
requests which got dispatched to views?
If you wanted to logic to be, "If a request doesn't match any pattern,
don't bother logging the 404 if the route looks like a static media file",
there could be some justification for that. But, not logging something
which matched and got dispatched is just plain wrong.
--
Ticket URL: <https://code.djangoproject.com/ticket/14800#comment:16>
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].
For more options, visit https://groups.google.com/groups/opt_out.
