[
https://issues.apache.org/jira/browse/SLING-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903047#action_12903047
]
Felix Meschberger commented on SLING-1410:
------------------------------------------
The vanity path functionality is what it is called: a vanity path. As such it
is supported unmodied (your first example) or with selectors and extensions
(your third) example. But the vanity path is not intended as an intermediate
node (your second sample).
You could use the /etc/map functionality though, to map a path prefix. See
http://sling.apache.org/site/mappings-for-resource-resolution.html
> VanityPath not working in middle of URL
> ---------------------------------------
>
> Key: SLING-1410
> URL: https://issues.apache.org/jira/browse/SLING-1410
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Environment: -r 911442, max osx 10.5, jdk 1.6 on karaf 1.2 using
> launchpad feature
> Reporter: Jason Rose
>
> $ curl -F "title=hello" -F"jcr:mixinTypes=sling:VanityPath"
> -F"sling:vanityPath=/nice/path"
> http://admin:ad...@localhost:8181/content/test/this/is/a/nasty/path
> $ curl -F"title=test"
> http://admin:ad...@localhost:8181/content/test/this/is/a/nasty/path/even/more/path
> Now, the inconsistency is here:
> $ curl localhost:8181/nice/path works as intended.
> $ curl localhost:8181/nice/path/even/more/path returns a 404
> $ curl localhost:8181/nice/path.infinity.json shows that the nodes are indeed
> there, but I can't seem to access them.
> Is this the intended behavior of the vanityPath, i.e. to not allow the path
> as part of the resource resolution process? It doesn't seem to be the case,
> since calling .infinity.json on the vanityPath shows the nodes I want to
> access under them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
