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 ed34237f0 Clarify terminology in resource resolution documentation
ed34237f0 is described below
commit ed34237f0e49bf50c0cce77da860326d59f08368
Author: Konrad Windszus <[email protected]>
AuthorDate: Tue Apr 14 18:04:27 2026 +0200
Clarify terminology in resource resolution documentation
---
.../the-sling-engine/mappings-for-resource-resolution.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
b/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
index bd79c0209..424fc84bf 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
@@ -10,7 +10,7 @@ tags=core,resources,resourcemappings
The
-1. resource resolution/incoming mapping (i.e. mapping a request path to a
resource in Sling's resource tree) as well as
+1. resource resolving (aka incoming mapping, i.e. mapping a request path to a
resource in Sling's resource tree) as well as
2. mapping a resource path to an external URL/path (aka reverse mapping or
outgoing mapping)
can be influenced in different ways:
@@ -37,7 +37,7 @@ The following properties in resource based mapping entries
are detected inside t
### Incoming Mapping
-Incoming mapping entries are matched against the request's *scheme*, *host*,
*port* and *uri path*. To accomplish this a virtual path is constructed from
the request like this `{scheme}/{host}.{port}/{uri_path}`. This string is then
matched against internal (incoming) mapping entries. The longest matching entry
string is used and the replacement, that is the redirection property, is
applied. There might even be multiple replacements for one entry, where the
first one retuning an existing [...]
+Incoming mapping (aka resolving) entries are matched against the request's
*scheme*, *host*, *port* and *uri path*. To accomplish this a virtual path is
constructed from the request like this `{scheme}/{host}.{port}/{uri_path}`.
This string is then matched against internal (incoming) mapping entries. The
longest matching entry string is used and the replacement, that is the
redirection property, is applied. There might even be multiple replacements for
one entry, where the first one retu [...]
### Mapping Entry Specification
