[ https://issues.apache.org/jira/browse/SLING-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014440#comment-17014440 ]
Carsten Ziegeler commented on SLING-7760: ----------------------------------------- Thanks, ok so this sounds like a context aware configuration to me. However, I would be worried of having such a dependency from the engine; in addition I'm worried about performance (figuring out with each and every request which context applies). Maybe it helps if we could see some examples for such per site headers > Sling Main Servlet - Change header configuration to a service > ------------------------------------------------------------- > > Key: SLING-7760 > URL: https://issues.apache.org/jira/browse/SLING-7760 > Project: Sling > Issue Type: Improvement > Reporter: Jason E Bailey > Assignee: Jason E Bailey > Priority: Major > > The ability to set headers must be done prior to any writing that occurs the > output stream. This is the reason why the headers are set to be configured in > the Sling Main Servlet. > With Sling being used to maintain multiple sites, having a single set of > response headers creates problems where the header provides a non tailored > response. One site may have a conflicting set of requirements then another > site. > If the setting of headers was moved from being a configuration to being a > service used by the Main Servlet, this would allow the following: > * Headers set on a per site basis > * Headers based on selected resource > * Ability to modify the headers without causing the restart of the Sling > Main Servlet > ** Which if you're dealing with CSP headers can be a constant pain > * Ability to create a CSP configuration Service that eases the use of CSP > creation > > -- This message was sent by Atlassian Jira (v8.3.4#803005)