loggerhead

404 Not Found responses aren't logged

Bug #381029 reported by Matt Nordhoff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
loggerhead
Fix Released
Low
Matt Nordhoff

Bug Description

If a request results in a 404 Not Found response, all that shows up in the log file is this:

DEBUG:paste.httpserver.ThreadPool:Added task (0 tasks queued)

No access log information or anything else.

Probably not a Loggerhead bug, but I didn't want to lose track of it.

Related branches

lp:loggerhead
Revision history for this message
Matt Nordhoff (mnordhoff) wrote :

Actually, it works fine in the branch I run on my website, with a custom serve-branches. (lp:~mnordhoff/loggerhead/cheezum)

Revision history for this message
Martin Albisetti (beuno) wrote :

not sure what's going on here.
Does your branch fix this?

Changed in loggerhead:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Matt Nordhoff (mnordhoff) wrote :

It's not intended to fix this bug. Like I said, that branch uses a custom serve-branches, with a different logging config, which I guess avoids this bug somehow.

404 responses are generated by raising an exception. My guess is that the logging app doesn't catch the exception, so it gets ignored. Maybe my branch decorates the apps in a different order that happens to work for some reason.

Revision history for this message
Matt Nordhoff (mnordhoff) wrote :

I was right. Making sure "TransLogger(app)" happens after "HTTPExceptionHandler(app)" fixed this, and I did it in r363.

Changed in loggerhead:
assignee: nobody → Matt Nordhoff (mnordhoff)
milestone: none → 1.16rc1
status: Triaged → Fix Committed
Martin Albisetti (beuno)
Changed in loggerhead:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.