Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Handling of Sling url selector and suffix

charlieshum
Level 1
Level 1

Hi. For example I have a path /en/example.html

At publisher
When there is selector and suffix added to a url and become /en/example.1.html/test.html

The node is resolvable (from recent request) but empty page is shown

 

This happens on the React SPA of WKND Guide.

I also tried on we.retail and seems working correctly, /content/we-retail/us/en.1.html/test.html  can show the content /content/we-retail/us/en.html 

 

How should selector and suffix be handled correctly? Actually would like to handle unknown selector and suffix as 404 content

1 Accepted Solution
Veena_Vikram
Correct answer by
Community Advisor
Community Advisor
2 Replies
Veena_Vikram
Correct answer by
Community Advisor
Community Advisor
charlieshum
Level 1
Level 1

These links are talking about the sling resolution on JSP page components. But how about the case of React SPA? Cannot find any article about selector and suffix handling on React SPA

Veena_Vikram
Community Advisor
Community Advisor

These stand true for HTL and JSPs. The resolution happens as per https://issues.apache.org/jira/browse/SLING-387 . I have to check how React SPA is structured. There won't be any big difference as the React components might be having a one on one relation with AEM components. And AEM components are written in HTL . I will still look into the React SPA and give more input on this.

charlieshum
Level 1
Level 1

Thanks for your reply. I have read this before, but what I need is the way to handle url selector and suffix on React SPA