sling-dev mailing list archives

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


Carsten Ziegeler commented on SLING-7760:

[~jebailey] I've created SLING-8991 to improve the handling of configuration changes - but
yes, that's independent of this issue here.
Do you really need a plugin model to delegate the work to custom services? Or would it be
possible do implement this based on configurations, for example with factory configurations
for header (each site having its own factory config).?

> 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