Adobe Experience Manager Sites & More

Ben_Newman_-_3S · 3/8/17

I'm manually creating vanity URLs on assets by setting the sling:vanityPath parameter under the asset's content node. This works fine for pages, and initially is working great for dam assets, but after rebooting the assets are no longer available under the vanity URLs and return a 404. Is there some other place I need to configure them?

smacdonald2008 · 3/9/17

Looks like AEM has a bug. I CAN reproduce this! I recommend opening a ticket so support can investigate.

View solution in original post

kautuk_sahni · 3/9/17

Hi,

The concept of vanity path is:

Go to the jcr:content node of Page/Asset and add a property "sling:vanityPath" with some "Value".

This will create a Vanity URL for that Node.

For Assets:

1. Go to the assets in crx/de

2. open jcr:content of that PDF/Image/Asste.

3. Add """sling:vanityPath" with some "Value"

Now open "http://localhost:4502/<Value>"

I tried this and it is working for me. Unable to reproduce this behavior.

~kautuk

Kautuk Sahni

Ben_Newman_-_3S · 3/9/17

Did you then shutdown and restart the server? We've tried this on multiple servers and multiple AEM versions now and the behavior is the same. The initial sling:vanityPath setting works, but after a restart it no longer does. Also it works for pages, just not assets. It looks like the Resource Resolver is only being initialized with vanityPaths from page assets.

smacdonald2008 · 3/9/17

Looks like AEM has a bug. I CAN reproduce this! I recommend opening a ticket so support can investigate.

smacdonald2008 · 3/9/17

After starting - what did work - renders:

<html> <head> <title>File not found</title> </head> <body> <p>A custom errorhandler for 404 responses</p> </body> </html>

Adobe Experience Manager Sites & More

AEM 6.0 vanity URLs under /content/dam unavailable after restart

Kautuk Sahni

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe