Vanity URL is not getting JCR:CONTENT

Avatar

Avatar
Level 1
naxtyn_
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
naxtyn_
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
naxtyn_
Level 1

04-05-2020

Hi there, 

 

I have a request where we need to collect some data from the components, so we need to consume the jcr:content.json but when a page have a vanity applied it responses with a 404. 

Page : /en/myvanitypage.html OK 200

jcr : /en/myvanitypage/_jcr_content.json 404 

 

Do you know if there is a bug here, i'm using aem OOB? 

 

Regards.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile
ArpitVarshney
MVP

04-05-2020

Hi @naxtyn_ 

a vanity URL is, “a unique web address that is branded for marketing purposes … a custom URL that exists to help users remember and find a specific page of your website.”

I think this is expected behaviour and not a bug. You need to use the actual url which point to corresponding node in aem to get the json of that page.

 

Regards,

Arpit

Answers (1)

Answers (1)

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

645 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

645 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

04-05-2020

When enabling "vanity URL" on a page, only the set value can be used to resolve the page. 

The value set as "/hello/world" resolves to the page "/hello/world.html" && "/hello/world.json", and throws a 404 not found when "/hello/world/jcr:content.json" is requested; this is expected.