sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Bailey (Jira)" <>
Subject [jira] [Commented] (SLING-7760) Sling Main Servlet - Change header configuration to a service
Date Fri, 10 Jan 2020 17:30:00 GMT


Jason Bailey commented on SLING-7760:

[~cziegeler] that would be a great step in the right direction. The reason why I would eventually
like to see it service based is that problem I'm having with different headers being required
for different domains that are all ran out of one instance of AEM. As well as doing cool things
with expiration headers and security headers.

> Sling Main Servlet - Change header configuration to a service
> -------------------------------------------------------------
>                 Key: SLING-7760
>                 URL:
>             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

View raw message