[
https://issues.apache.org/jira/browse/SLING-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648079#comment-15648079
]
Rob Ryan commented on SLING-4604:
---------------------------------
*If* content-type is being reset to the same value it has already been set to
you are correct the downstream setContentType will not be called. Do you have a
use case where that is problematic? Off hand I don't see how suppressing a set
to the same value should have any logical impact.
> Multiple Content-Disposition headers added
> ------------------------------------------
>
> Key: SLING-4604
> URL: https://issues.apache.org/jira/browse/SLING-4604
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Security 1.0.10
> Reporter: Rob Ryan
> Assignee: Antonio Sanso
> Fix For: Security 1.0.12
>
> Attachments: 4604patch.txt
>
>
> Multiple content-disposition headers can be added under some conditions.
> This seems to happen because setContentType is actually called more than once
> for the same response when multiple sling scripts are involved in rendering,
> e.g. via
> org.apache.sling.scripting.core.impl.DefaultSlingScript.service(javax.servlet.ServletRequest,
> javax.servlet.ServletResponse) line: 448
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
