You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/12/21 18:18:18 UTC

[jira] Closed: (SLING-926) Do not render directory on included request

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

Carsten Ziegeler closed SLING-926.
----------------------------------


> Do not render directory on included request
> -------------------------------------------
>
>                 Key: SLING-926
>                 URL: https://issues.apache.org/jira/browse/SLING-926
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Get 2.0.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Servlets Get 2.0.8
>
>
> As of SLING-723, the StreamRendererServlet contains functionality to render an index (directory listing) or send 403/FORBIDDEN if rendering the index is disabled by configuration.
> This works like this:
>    * If request has trailing slash -> render directory or send 403
>    * Else If resource adapts to a stream -> spool the stream
>    * Else redirect to the same URL with a trailing slash
> This all perfectly works if this mechanism handles the request directly. If this mechanism is triggered in an included resource, where a directly addressed resource includes another resource, which is then handled by the StreamRendererServlet, this should probably be different:
>    * If the resource adapts to a stream -> spool the stream
>    * Else do nothing (but log this situation and add an entry in the RequestProgressTracker

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