incubator-wink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Rheinheimer (JIRA)" <>
Subject [jira] Created: (WINK-223) reduce log output on 404s
Date Mon, 02 Nov 2009 22:46:59 GMT
reduce log output on 404s

                 Key: WINK-223
             Project: Wink
          Issue Type: Improvement
          Components: Server
    Affects Versions: 1.1
            Reporter: Mike Rheinheimer
             Fix For: 1.1

Opinion needed:  do we need to reduce the amount of output that is logged when a 404 is issued
from the server?

The logging occurs in org.apache.wink.server.internal.RequestProcessor.logException.  Note
that in all cases, the stack trace will be printed.  Specifically, a 404 will land in the, and will print a full stack trace to the log.  Is this really necessary?

On the one hand, it may be valuable to see which handler determined that a client has targetted
a missing resource.  On the other hand, info is probably sufficient.  Also, consider what
happens when a malicious client comes along trying to fill up server logs or otherwise hack
a server by hitting any and all URLs and resource it can.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message