Hi, IIUC, this is by design. Vanity paths are intended for inbound use only.
Regards, Justin On Fri, Dec 16, 2016 at 4:57 AM Antonio Sanso <[email protected]> wrote: > hi *, > > I would have a question about VanityPath and ResourceResolver#map . > Assuming I have a resource /content/foo/bar with a vanity path set ti > /bar . > AFAICS if I try to do ResourceResolver#map("/content/foo/bar”) the > expectation give by the ResourceResolver#map API would be that this would > return “/bar" . > Unfortunately this is not the case . This is still returning > "/content/foo/bar” . > It looks like this mapping mechanism works fine for alias and etc/map but > not for vanity path. > AFAICR this has been like this since the begin (aka no regression) > My question is this a bug or is by design ? > > I hope someone can clarify this… > > regards > > antonio
