[ https://issues.apache.org/jira/browse/SLING-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-287. ----------------------------------- Resolution: Fixed Fixed as described in Rev. 631943: > Modify DefaultServlet of the servlet resolver bundle to send failure status > --------------------------------------------------------------------------- > > Key: SLING-287 > URL: https://issues.apache.org/jira/browse/SLING-287 > Project: Sling > Issue Type: Improvement > Components: ServletResolver > Reporter: Felix Meschberger > Assignee: Felix Meschberger > Fix For: 2.0.0 > > > Currently the DefaultServlet implements partly the same functionality as the > sling/servlets-default module. For one thing this is bad due to duplicate > code. Another bad thing, and even worse probably, is that this might create > difficult to resolve issues. Consider for example sling/servlets-default not > be installed and a request being placed. It may be that the DefaultServlet > may handle the request just as if sling/servlets-default would be installed. > Now a request is placed, which would be handled by sling/servlets-default but > is not handled by DefautlServlet. Now the confusion starts as to why this > situation happens. > I propose to change the DefaultServlet such, that ... > * 404/NOT FOUND is sent if the request resource is a MissingResource > * 500/INTERNAL SERVER ERROR is sent if the resource exists but no > registered Servlet or Script could be found > See also the dev list discussion [1] > [1] http://www.mail-archive.com/sling-dev@incubator.apache.org/msg02995.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.