[SLING-6561] Test case for SLING-6271

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Done
• Fix Version/s: Security 1.1.4
• Component/s: Extensions
• Assignee: Antonio Sanso
• Reporter: Rob Ryan
• Created: 23/Feb/17 18:41
• Updated: 13/Jun/17 12:45
• Resolved: 24/Feb/17 12:31

Description

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.