You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Christian Oldiges (JIRA)" <ji...@apache.org> on 2010/03/22 16:31:27 UTC
[jira] Created: (WICKET-2794) Not all exceptions are properly
handled by the WicketFilter -> results in empty response document with
unset status code -> seen as HTTP_OK by client
Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: WICKET-2794
URL: https://issues.apache.org/jira/browse/WICKET-2794
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.4.7
Reporter: Christian Oldiges
Priority: Minor
Our custom ResourceStreamLocator might throw RuntimeExceptions.
When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.
quickstart follows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-2794) Not all exceptions are properly
handled by the WicketFilter -> results in empty response document with
unset status code -> seen as HTTP_OK by client
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg reassigned WICKET-2794:
-------------------------------------
Assignee: Igor Vaynberg
> Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2794
> URL: https://issues.apache.org/jira/browse/WICKET-2794
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Christian Oldiges
> Assignee: Igor Vaynberg
> Priority: Minor
> Attachments: wicket2794.zip
>
>
> Our custom ResourceStreamLocator might throw RuntimeExceptions.
> When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.
> quickstart follows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2794) Not all exceptions are properly
handled by the WicketFilter -> results in empty response document with
unset status code -> seen as HTTP_OK by client
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2794.
-----------------------------------
Fix Version/s: 1.4.11
1.5-M2
Resolution: Fixed
> Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2794
> URL: https://issues.apache.org/jira/browse/WICKET-2794
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Christian Oldiges
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.11, 1.5-M2
>
> Attachments: wicket2794.zip
>
>
> Our custom ResourceStreamLocator might throw RuntimeExceptions.
> When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.
> quickstart follows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2794) Not all exceptions are properly
handled by the WicketFilter -> results in empty response document with
unset status code -> seen as HTTP_OK by client
Posted by "Christian Oldiges (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Oldiges updated WICKET-2794:
--------------------------------------
Attachment: wicket2794.zip
quickstart
> Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2794
> URL: https://issues.apache.org/jira/browse/WICKET-2794
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Christian Oldiges
> Priority: Minor
> Attachments: wicket2794.zip
>
>
> Our custom ResourceStreamLocator might throw RuntimeExceptions.
> When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.
> quickstart follows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2794) Not all exceptions are properly
handled by the WicketFilter -> results in empty response document with
unset status code -> seen as HTTP_OK by client
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902278#action_12902278 ]
Hudson commented on WICKET-2794:
--------------------------------
Integrated in Apache Wicket 1.5.x #263 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/263/])
Issue: WICKET-2794
> Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2794
> URL: https://issues.apache.org/jira/browse/WICKET-2794
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Christian Oldiges
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.11, 1.5-M2
>
> Attachments: wicket2794.zip
>
>
> Our custom ResourceStreamLocator might throw RuntimeExceptions.
> When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.
> quickstart follows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2794) Not all exceptions are properly
handled by the WicketFilter -> results in empty response document with
unset status code -> seen as HTTP_OK by client
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902277#action_12902277 ]
Hudson commented on WICKET-2794:
--------------------------------
Integrated in Apache Wicket 1.4.x #116 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/116/])
Issue: WICKET-2794
> Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2794
> URL: https://issues.apache.org/jira/browse/WICKET-2794
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Christian Oldiges
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.11, 1.5-M2
>
> Attachments: wicket2794.zip
>
>
> Our custom ResourceStreamLocator might throw RuntimeExceptions.
> When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.
> quickstart follows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.