[
https://issues.apache.org/jira/browse/SLING-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Peter updated SLING-3119:
-----------------------------
Description:
The current StartupFilter implementation is a Sling filter which prevents
requests from being processed only after all HTTP filters have been called and
authentication has been handled.
Making this an HTTP filter registered with the Felix ExtHttpService would
answer requests with 503 much earlier.
Such a filter must still allow access to felix.webconsole.manager.root,
typically /system/console
was:
The current {{StartupFilter}} implementation is a Sling filter which prevents
requests from being processed only after all HTTP filters have been called and
authentication has been handled.
Making this an HTTP filter registered with the Felix {{ExtHttpService}} would
answer requests with 503 much earlier.
Such a filter must still allow access to {{felix.webconsole.manager.root}},
typically {{/system/console}}
> Startup Filter: move to HTTP filter to prevent authentication before startup
> has completed
> ------------------------------------------------------------------------------------------
>
> Key: SLING-3119
> URL: https://issues.apache.org/jira/browse/SLING-3119
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Ben Peter
> Priority: Minor
>
> The current StartupFilter implementation is a Sling filter which prevents
> requests from being processed only after all HTTP filters have been called
> and authentication has been handled.
> Making this an HTTP filter registered with the Felix ExtHttpService would
> answer requests with 503 much earlier.
> Such a filter must still allow access to felix.webconsole.manager.root,
> typically /system/console
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
