[
https://issues.apache.org/jira/browse/SLING-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-1069:
---------------------------------------
Attachment: SLING-1069-test.patch
Integration tests for this change - currently fails, but saving here for future
use.
Playing with that shows that there's a deeper issue: it seems like all servlet
registration parameters are ORed, whereas ANDing them seems much more logical
from the user's point of view. I'll discuss that on the dev list.
> Servlets registered with for resourceTypes = sling/servlet/default responds
> to all extensions
> ---------------------------------------------------------------------------------------------
>
> Key: SLING-1069
> URL: https://issues.apache.org/jira/browse/SLING-1069
> Project: Sling
> Issue Type: Bug
> Components: Servlets Resolver
> Affects Versions: Servlets Resolver 2.0.4
> Reporter: Vidar S. Ramdal
> Fix For: Servlets Resolver 2.0.8
>
> Attachments: RogueServlet.java, SLING-1069-test.patch,
> SLING-1069.patch
>
>
> A servlet registered with
> @scr.property name="sling.servlet.extensions" value="html"
> @scr.property name="sling.servlet.resourceTypes"
> value="sling/servlet/default"
> in the Javadoc, responds to all requests, in effect ignoring the
> "sling.servlet.extensions" property.
> To reproduce:
> 1. Install servlet from attachment (coming up)
> 2. Let the browser fetch /somenode.json
> Expected result:
> The server returns the JSON rendering of /somenode
> Actual result:
> The server returns "Rogue Servlet"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
