You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sebastiaan van Erk (JIRA)" <ji...@apache.org> on 2008/12/22 20:40:46 UTC
[jira] Created: (WICKET-1991) SharedResourceRequestTarget logs
ERRORs to the logfile on 404 (client errors)
SharedResourceRequestTarget logs ERRORs to the logfile on 404 (client errors)
-----------------------------------------------------------------------------
Key: WICKET-1991
URL: https://issues.apache.org/jira/browse/WICKET-1991
Project: Wicket
Issue Type: Bug
Affects Versions: 1.4-RC1
Reporter: Sebastiaan van Erk
Priority: Minor
Attachments: patch
Client errors are not programming errors, nor fatal errors, nor errors realy at all on the server side. The server should just handle it as a normal occurrence (a resource is requested that does not exist, i.e., 404).
I agree that the current log statements are useful for development/debugging purposes, so I suggest to demote the log.error statements in the respond method to log.debug statements.
Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1991) SharedResourceRequestTarget logs
ERRORs to the logfile on 404 (client errors)
Posted by "Sebastiaan van Erk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastiaan van Erk updated WICKET-1991:
---------------------------------------
Affects Version/s: 1.3.5
> SharedResourceRequestTarget logs ERRORs to the logfile on 404 (client errors)
> -----------------------------------------------------------------------------
>
> Key: WICKET-1991
> URL: https://issues.apache.org/jira/browse/WICKET-1991
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.5, 1.4-RC1
> Reporter: Sebastiaan van Erk
> Priority: Minor
> Attachments: patch
>
>
> Client errors are not programming errors, nor fatal errors, nor errors realy at all on the server side. The server should just handle it as a normal occurrence (a resource is requested that does not exist, i.e., 404).
> I agree that the current log statements are useful for development/debugging purposes, so I suggest to demote the log.error statements in the respond method to log.debug statements.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1991) SharedResourceRequestTarget logs
ERRORs to the logfile on 404 (client errors)
Posted by "Sebastiaan van Erk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastiaan van Erk updated WICKET-1991:
---------------------------------------
Attachment: patch
> SharedResourceRequestTarget logs ERRORs to the logfile on 404 (client errors)
> -----------------------------------------------------------------------------
>
> Key: WICKET-1991
> URL: https://issues.apache.org/jira/browse/WICKET-1991
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.4-RC1
> Reporter: Sebastiaan van Erk
> Priority: Minor
> Attachments: patch
>
>
> Client errors are not programming errors, nor fatal errors, nor errors realy at all on the server side. The server should just handle it as a normal occurrence (a resource is requested that does not exist, i.e., 404).
> I agree that the current log statements are useful for development/debugging purposes, so I suggest to demote the log.error statements in the respond method to log.debug statements.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1991) SharedResourceRequestTarget logs
ERRORs to the logfile on 404 (client errors)
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-1991.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC2
Assignee: Juergen Donnerstag
changed it to log.info
> SharedResourceRequestTarget logs ERRORs to the logfile on 404 (client errors)
> -----------------------------------------------------------------------------
>
> Key: WICKET-1991
> URL: https://issues.apache.org/jira/browse/WICKET-1991
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.5, 1.4-RC1
> Reporter: Sebastiaan van Erk
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.4-RC2
>
> Attachments: patch
>
>
> Client errors are not programming errors, nor fatal errors, nor errors realy at all on the server side. The server should just handle it as a normal occurrence (a resource is requested that does not exist, i.e., 404).
> I agree that the current log statements are useful for development/debugging purposes, so I suggest to demote the log.error statements in the respond method to log.debug statements.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.