This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 96a96f1ad Update URL decomposition documentation for clarity
96a96f1ad is described below
commit 96a96f1ad3d8b7cfbe235d483e24857a13a37f74
Author: Konrad Windszus <[email protected]>
AuthorDate: Tue Oct 6 12:42:02 2026 +0200
Update URL decomposition documentation for clarity
Clarified the explanation regarding resource path decomposition and the
handling of dots in resource names.
---
.../jbake/content/documentation/the-sling-engine/url-decomposition.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
b/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
index d5800acaa..33de97d5c 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
@@ -11,7 +11,7 @@ During the *Resource Resolution* step, the client request URI
(as being returned
1. **Resource Path** - For existing resources the resource path is the longest
match (also considering its
[mappings](/documentation/the-sling-engine/mappings-for-resource-resolution.html))
pointing to a resource where the next character is either a dot (`.`) or it is
the full request URI.
Otherwise (for a path not matching any existing resource) this contains the
-*full request URI* (including extensions, selectors and suffix if existing).
The exact logic for retrieving the resource path is implemented at
[ResourceResolver.resolve(HttpServletRequest,
String)](https://sling.apache.org/apidocs/sling11/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-)
called from `org.apache.sling.engine.impl.request.RequestData.initResource()`
with the 2nd argument being the request path. *It is imp [...]
+*full request URI* (including extensions, selectors and suffix if existing).
The exact logic for retrieving the resource path is implemented at
[ResourceResolver.resolve(HttpServletRequest,
String)](https://sling.apache.org/apidocs/sling11/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-)
called from `org.apache.sling.engine.impl.request.RequestData.initResource()`
with the 2nd argument being the request path. *It is imp [...]
1. **Selectors** - If the first character in the request URL after the
resource path is a dot (`.`), the string after the dot up to but not including
the last dot before the next slash character or the end of the request URL
comprises the selectors. If the resource path spans the complete request URL no
selectors exist. If only one dot follows the resource path before the end of
the request URL or the next slash, also no selectors exist. For non-existing
resources the selectors are the [...]
1. **Extension** - The string after the last dot after the resource path in
the request URL but before the end of the request URL or the next slash after
the resource path in the request URL is the extension. For non-existing
resources just the part after the last dot of the request URI.
1. **Suffix** - If the request URL contains a slash character after the
resource path and optional selectors and extension, the path starting with the
slash up to the end of the request URL is the suffix path. Otherwise, the
suffix path is empty. Note, that after the resource path at least a dot must be
in the URL to let Sling detect the suffix.
