[
https://issues.apache.org/jira/browse/SLING-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-6499.
----------------------------------
> SlingDavExServlet protectedhandlers-config parameter not propagated to
> ServletConfig
> ------------------------------------------------------------------------------------
>
> Key: SLING-6499
> URL: https://issues.apache.org/jira/browse/SLING-6499
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Critical
> Fix For: JCR Davex 1.3.8
>
>
> I've noticed while testing the new 1.3.6 release that a warning is logged
> when starting up the Launchpad:
> {noformat}30.01.2017 18:14:04.829 *WARN* [Apache Sling Repository Startup
> Thread] org.apache.jackrabbit.server.remoting.davex.ProtectedRemoveManager
> protectedhandlers-config is missing -> DIFF processing can fail for the
> Remove operation if the content toremove is protected!{noformat}
> Tracing back the code, I see that the service registration parameters are
> properly added in {{SlingDavExServlet.activate}}:
> {noformat}initProps = {servlet.init.csrf-protection=disabled,
> servlet.init.resource-path-prefix=/crx/server, service.vendor=The Apache
> Software Foundation, sling.auth.requirements=-/crx/server,
> protectedhandlers-config=org.apache.jackrabbit.server.remoting.davex.AclRemoveHandler,
> osgi.http.whiteboard.servlet.pattern=/crx/server/*,
> servlet.init.createAbsoluteURI=true, service.description=Sling JcrRemoting
> Servlet,
> osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=DavExAuthHttpContext)}{noformat}
> but they are not propagated to {{JcrRemotingServlet.init}}
> {noformat}config =
> org.apache.felix.http.base.internal.handler.ServletConfigImpl@3a275518
> {
> context =
> org.apache.felix.http.base.internal.whiteboard.PerBundleServletContextImpl@1107e18,
> initParams = {csrf-protection=disabled, createAbsoluteURI=true,
> resource-path-prefix=/crx/server}
> name = org.apache.sling.jcr.davex.impl.servlets.SlingDavExServlet
> }
> {noformat}
> This reverting the fix for SLING-6378 solves the issue, but I'd like to not
> revert that and instead find the root cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
