Hello All,
I've started using the sling:VanityPath mixin to allow users to access
my content in a much cleaner fashion, but I've started to hit some
sort of problem when incorporating them with posts. For example,
$ 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 "property=xyz" http://admin:ad...@localhost:8181/nice/path/xyz
If I then browse to localhost:8181/nice/path.infinity.json, I don't
see the xyz node in the list. Similarly, if I navigate to the
original path, the xyz node isn't there either.
This becomes a problem when I try to upload files to the "nasty" url
then attempt to access them via the vanity path. It just doesn't work:
$ curl -F"[email protected]" -F"title=hello" -
F"jcr:mixinTypes=sling:VanityPath" -F"sling:vanityPath=/nice/path2" http://admin:ad...@localhost:8181/content/test/this/is/a/nasty/path2
http://localhost:8181/content/test/this/is/a/nasty/path2/file.txt
works just fine, as expected.
http://localhost:8181/nice/path2/file.txt returns a 404.
I'm not quite sure what is happening here and if it is intended
behavior, but as it is, vanity urls don't seem to be behaving
properly. Is this a bug, and if it isn't, what are my options in
working around this behavior?
Thank you,
-Jason
