[
https://issues.apache.org/jira/browse/SLING-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027659#comment-17027659
]
Bertrand Delacretaz commented on SLING-7760:
--------------------------------------------
bq. create a service interface that takes the request path..
Why not the Resource object? Headers like cache-control often depend on that.
bq. and returns a list of headers that applies to that request....
Passing an interface that allows for directly setting the headers would avoid
having to set them twice.
> 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)
