Author: kwin
Date: Thu Sep 22 12:09:12 2016
New Revision: 1761919
URL: http://svn.apache.org/viewvc?rev=1761919&view=rev
Log:
clarify even further that the first dot in the URL is not always separating
resource path from the rest
Modified:
sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext
Modified:
sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext?rev=1761919&r1=1761918&r2=1761919&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext
(original)
+++
sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext
Thu Sep 22 12:09:12 2016
@@ -6,7 +6,7 @@ Title: URL decomposition
During the *Resource Resolution* step, the client request URI (as being
returned by
[HttpServletRequest.getRequestURI()](http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getRequestURI()))
is decomposed into the following parts (in exactly this order):
1. **Resource Path** - For existing resources the resource path is the longest
match (also considering its [mappings]({{
refs.mappings-for-resource-resolution.path }})) 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) the resource path
ends at the *first dot (`.`)* in the request url. The exact logic for
retrieving the resource path is implemented at
[ResourceResolver.resolve(HttpServletRequest,String)](https://sling.apache.org/apidocs/sling7/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-).
*It is impossible to tell from just looking at the request URI where the
resource path part ends. You have to know the underlying resource structure to
know how a URL is decomposed*.
+Otherwise (for a path not matching any existing resource) the resource path
ends at the *first dot (`.`)* in the request url. The exact logic for
retrieving the resource path is implemented at
[ResourceResolver.resolve(HttpServletRequest,String)](https://sling.apache.org/apidocs/sling7/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-).
*It is impossible to tell from just looking at the request URI where the
resource path part ends. You have to know the underlying resource structure to
know how a URL is decomposed. You cannot safely assume that the resource path
will always end at the first dot!*.
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.
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.
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.
