[ https://issues.apache.org/jira/browse/SLING-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416257#comment-13416257 ]
Carsten Ziegeler commented on SLING-2533: ----------------------------------------- Maybe supporting the accept header directly in Sling would be a good idea - not really sure. This is not the first time I hear the request for it :) So far, users solved it by having a request filter upfront which checked if there is no extension but a usable accept header and then simply rewrote the request url path by appending the correct extension. All requests getting into Sling use a proper extension. Not the nicest solution but does the trick. > ResourceCollector fails to resolve selector scripts when no extension is used > ----------------------------------------------------------------------------- > > Key: SLING-2533 > URL: https://issues.apache.org/jira/browse/SLING-2533 > Project: Sling > Issue Type: Bug > Components: Servlets > Affects Versions: Servlets Resolver 2.1.2 > Environment: this applies to version 2.1.3-SNAPSHOT > Reporter: Tyson Norris > Attachments: sling-2533.patch > > > A specific use case where this comes up is: > request: http://localhost:4502/content/test/include > In JCR repo: > - node at content/test/include has sling:resourceType=test/main > - script to render this resource is /apps/test/main/GET.jsp > - script to render different type with selector referneced via: > <sling:include resourceType="test/sometype" replaceSelectors="special"/> > - script to render the different type is /apps/test/sometype/special.jsp > in this case, special.jsp script is only resoved if renamed to special.GET.jsp > Note that: > - no extension on requested URL > - using a replaced selector in sling:include should behave similar to > specifying an exentsion when the extension is null, I think. > See attached patch to ResourceCollector and ScriptSelectionTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira