You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/01/28 15:05:36 UTC
[jira] Created: (SLING-207) Status code 500 not reported to client
for infinite loop in sling.include
Status code 500 not reported to client for infinite loop in sling.include
-------------------------------------------------------------------------
Key: SLING-207
URL: https://issues.apache.org/jira/browse/SLING-207
Project: Sling
Issue Type: Bug
Reporter: Bertrand Delacretaz
Priority: Minor
See TODO_FAILS_ in launchpad-webapp IncludeTest class, testInfiniteLoopDetection() method.
The DefaultErrorHandlerServlet correctly calls response.setStatus(500) in this case, but the client receives a status 200.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-207) Status code 500 not reported to
client for infinite loop in sling.include
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563156#action_12563156 ]
Bertrand Delacretaz commented on SLING-207:
-------------------------------------------
To clarify, the status 500 is caused by an include such as the one below:
<html>
<body>
<%
sling.include(resource.getPath() + ".html");
%>
</body>
</html>
The infinite loop is now detected correctly, but the client still receives an HTTP 200 response.
> Status code 500 not reported to client for infinite loop in sling.include
> -------------------------------------------------------------------------
>
> Key: SLING-207
> URL: https://issues.apache.org/jira/browse/SLING-207
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> See TODO_FAILS_ in launchpad-webapp IncludeTest class, testInfiniteLoopDetection() method.
> The DefaultErrorHandlerServlet correctly calls response.setStatus(500) in this case, but the client receives a status 200.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-207) Status code 500 not reported to client
for infinite loop in sling.include
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-207.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Felix Meschberger
Loop detection works and is correctly reported as status 500. Therefore I reactivated the respective integration test in Rev. 636532.
So, I also close this issue.
> Status code 500 not reported to client for infinite loop in sling.include
> -------------------------------------------------------------------------
>
> Key: SLING-207
> URL: https://issues.apache.org/jira/browse/SLING-207
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: 2.0.0
>
>
> See TODO_FAILS_ in launchpad-webapp IncludeTest class, testInfiniteLoopDetection() method.
> The DefaultErrorHandlerServlet correctly calls response.setStatus(500) in this case, but the client receives a status 200.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.