A developer has created a component with these fields:
Which HTL code and resulting valid URL path are generated?
In Sling URL decomposition, the suffix is the path segment that follows the resource path and its extension. Content meant to be displayed as a suffix must therefore be appended after the page path and the .html extension, producing /content/testsite/en/page1.html/product/test1. Sling resolves this URL to the existing page1 resource and exposes /product/test1 as the request suffix, so the link remains valid. Inserting the extra segment before .html would instead address /content/testsite/en/page1/product/test1, a resource that does not exist, so that link would not resolve.
.html
/content/testsite/en/page1.html/product/test1
page1
/product/test1
/content/testsite/en/page1/product/test1
Community Discussion