Handling of Sling url selector and suffix

Question

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

VeenaVikraman · Accepted Answer

@charlieshum /content/we-retail/us/en.1.html/test.html looks like an invalid sling to me to be resolved. I couldn't understand your question completely , but still I have compiled some Sling Resolution related links for your better understnading. Hope this helps.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-script-resolution/qaq-p/281048

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-script-resolution-best-explained/td-p/250521

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-resolution/qaq-p/355911

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/template-component-can-t-override-page-html/qaq-p/292567

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-resource-resolution-preference/qaq-p/249373