[jira] Reopened: (SLING-1231) Send 404/NOT FOUND if default GET servlet has no renderer for an extension

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz reopened SLING-1231:
----------------------------------------

      Assignee: Bertrand Delacretaz  (was: Felix Meschberger)

Some integration tests need to be modified accordingly

> Send 404/NOT FOUND if default GET servlet has no renderer for an extension
> --------------------------------------------------------------------------
>
>                 Key: SLING-1231
>                 URL: https://issues.apache.org/jira/browse/SLING-1231
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Get 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Bertrand Delacretaz
>             Fix For: Servlets Get 2.0.8
>
>
> The DefaultGetServlet currentls sends a 403/FORBIDDEN status if a request cannot be handled because there is no renderer for the requested extension. Likewise the StreamRendererServlet also sends a 403/FORBIDDEN if called with the wrong extension (only res and no extension are allowed).
> This contrasts to the situation when a non-existing resource is requested: Consider http://host/notfound.html. This results in a 404/NOT FOUND response. If requesting http://host/notfound.XYZ and there is no renderer for the XYZ extension, a 403/FORBIDDEN status is returned. This is unexpected.
> Additionally, not having a renderer for a certain extension means that the resource cannot be rendered which is practically the same as if the resource would not exist -- rather than access to the resource is denied.

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