You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Antonio Sanso (JIRA)" <ji...@apache.org> on 2017/02/24 12:31:44 UTC
[jira] [Commented] (SLING-6561) Test case for SLING-6271
[ https://issues.apache.org/jira/browse/SLING-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882569#comment-15882569 ]
Antonio Sanso commented on SLING-6561:
--------------------------------------
applied patch from [~rryan@adobe.com] in r1784271 . Thanks
> Test case for SLING-6271
> ------------------------
>
> Key: SLING-6561
> URL: https://issues.apache.org/jira/browse/SLING-6561
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Rob Ryan
> Assignee: Antonio Sanso
> Priority: Minor
> Attachments: sling6271test.patch
>
>
> Attached is a proposed unit test for the issue reported in SLING-6271.
> In the case of setContentType being called before and after requestDispatcher.forward() each with the same content type SLING-6271 reported that the response ended up with no content type header.
> The key aspect of forward() was that it calls reset() which clears all headers on the response.
> The attached patch adds test cases for two scenarios around this: in case a content disposition header is also needed, or in case a content disposition header is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)