Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

AEM6.5 Personalization : 403 Error for matched experience having duplicate .default.html extension

Avatar

Level 1

We are trying to leverage aem personalization for content targeting using contexthub targeting engine

On authoring its working fine but on publish site I'm getting 403 error due to wrong path to target experience. 

 

Wrong path  : https://www.samplesite.ca/en/personalization-page/_jcr_content/root/responsivegrid/banner.html.defau...

 

Should be  : https://www.samplesite.ca/en/personalization-page/_jcr_content/root/responsivegrid/banner.default.ht...

 

Does anyone know any possible root cause or faces similar issue in past? Let me know if you need any further information. 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

403 error is usually for access issues. Can you confirm if the user is logged in as admin even in that scenario this error is seen?

Also we need to check everyone user's permissions.

 

Looking at the placement of html in wrong path (The selector is added after forming the html based url)), can you check if you have any custom code that adds a .html to a resource path. Can't recall any ootb service that does this. May be link externalizer.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

403 error is usually for access issues. Can you confirm if the user is logged in as admin even in that scenario this error is seen?

Also we need to check everyone user's permissions.

 

Looking at the placement of html in wrong path (The selector is added after forming the html based url)), can you check if you have any custom code that adds a .html to a resource path. Can't recall any ootb service that does this. May be link externalizer.