[
https://issues.apache.org/jira/browse/SLING-11514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-11514.
--------------------------------------
Resolution: Fixed
And wrap response in include if option is set:
https://github.com/apache/sling-org-apache-sling-engine/commit/5b8354ac62b712aa162222c1fd301a351dfb9bac
> Provide dispatcher option to ignore header changes on include
> -------------------------------------------------------------
>
> Key: SLING-11514
> URL: https://issues.apache.org/jira/browse/SLING-11514
> Project: Sling
> Issue Type: New Feature
> Components: API, Engine
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: API 2.26.0, Engine 2.9.4
>
>
> The servlet specification states in section 9.3 that on dispatcher include
> (not forward), all changes to headers from the include must be ignored.
> As Sling is following the servlet spec for includes and forwards, Sling
> should do the same. However, after 15 years of allowing an include to change
> headers, this has a large potential to break existing applications.
> Therefore we should rather provide a dispatcher option, that can be set to
> force this new behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
