Hi, On Tue, Dec 3, 2019 at 3:54 PM Bertrand Delacretaz <[email protected]> wrote: > ...For SLING-8110 I'd like to take into account the > sling.servlet.extensions and sling.servlet.methods properties... ... > To keep backwards compatibility, I suggest adding a new optional > sling.servlet.resolution property that for now can have the value > "strict".
I'm (at last) implementing this. Carsten observed in this thread that the meaning of "strict" is not really obvious here so I suggest instead: sling.servlet.extpaths = true To activate the SLING-8110 behavior that takes extension, selectors and HTTP method into account if this property is set on a path-mounted servlet and if the other existing corresponding properties are set. This can either mean "extended path-based servlet selection" or "extension etc. is taken into account". What do people think? -Bertrand (oh no - a naming discussion ;-)
