You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/11/24 14:14:00 UTC
[jira] [Assigned] (SLING-6316) Clarify description of
Content-Disposition-Filter configuration
[ https://issues.apache.org/jira/browse/SLING-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus reassigned SLING-6316:
--------------------------------------
Assignee: Antonio Sanso (was: Konrad Windszus)
> Clarify description of Content-Disposition-Filter configuration
> ---------------------------------------------------------------
>
> Key: SLING-6316
> URL: https://issues.apache.org/jira/browse/SLING-6316
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Security 1.1.2
> Reporter: Konrad Windszus
> Assignee: Antonio Sanso
> Attachments: SLING-6316-v01.patch
>
>
> From the description of the Apache "Sling Content Disposition Filter" component (https://github.com/apache/sling/blob/02fb326a008418c51482090814e4bff3cac657c7/contrib/extensions/security/src/main/java/org/apache/sling/security/impl/ContentDispositionFilter.java#L52) it is not clear, that under all circumstances the {{content-disposition:attachment}} is only then set if on the current resource either a {{jcr:data}} or {{jcr:content/jcr:data}} property is found. That is important information when you want to understand/configure the filter correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)