[sling-site] branch master updated: clarify path referring to the resource path (not request path)

[kw...@apache.org]

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 11928cf  clarify path referring to the resource path (not request path)
11928cf is described below

commit 11928cf594128c2a823bae774cb06055d1db6c7c
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Fri Feb 28 09:32:41 2020 +0100

    clarify path referring to the resource path (not request path)
---
 src/main/jbake/content/documentation/the-sling-engine/filters.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/main/jbake/content/documentation/the-sling-engine/filters.md b/src/main/jbake/content/documentation/the-sling-engine/filters.md
index 99eeddb..d4669a8 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/filters.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/filters.md
@@ -21,7 +21,7 @@ For Sling to pick up a `javax.servlet.Filter` service for filter processing two
 |---|---|---|---|---|
 | `sling.filter.scope` | `String`, `String[]` or `Vector<String>` | `request` | `REQUEST`, `INCLUDE`, `FORWARD`, `ERROR`, `COMPONENT` | Indication of which chain the filter should be added to. This property is required. If it is missing from the service, the service is ignored because it is assumed another consumer will be interested in using the service. Any unknown values of this property are also ignored causing the service to be completely ignored if none of the values provided by th [...]
 | `service.ranking` | `Integer` | `0` | Any `Integer` value | Indication of where to place the filter in the filter chain. The higher the number the earlier in the filter chain. This value may span the whole range of integer values. Two filters with equal `service.ranking` property value (explicitly set or default value of zero) will be ordered according to their `service.id` service property as described in section 5.2.5, Service Properties, of the OSGi Core Specification R 4.2. |
-| `sling.filter.pattern` | `String`| `(-)` | Any `String` value | Restrict the filter to paths that match the supplied regular expression. Requires Sling Engine 2.4.0. |
+| `sling.filter.pattern` | `String`| `(-)` | Any `String` value | Restrict the filter to resource paths that match the supplied regular expression. *This does not refer to the request path, but rather to the resolved resource path excluding selectors, extension and suffix* Requires Sling Engine 2.4.0. |
 | `sling.filter.suffix.pattern` | `String`| `(-)` | Any `String` value | Restrict the filter to requests with suffix that match the supplied regular expression. Requires Sling Engine 2.6.14. |
 | `sling.filter.selectors` | `String[]`| `(-)` | Any `String` value | Restrict the filter to requests whose selectors match one or more of the provided ones. Requires Sling Engine 2.6.14. |
 | `sling.filter.methods` | `String[]`| `(-)` | Any `String` value | Restrict the filter to requests whose methods match one or more of the provided ones. Requires Sling Engine 2.6.14. |
@@ -30,7 +30,7 @@ For Sling to pick up a `javax.servlet.Filter` service for filter processing two
 
 ## SlingServletFilter Annotation
 
-Coding the above being a bit tedious, `Apache Sling Servlets Annotations 1.1.0` provides handy `SlingServletFilter annotation to set those values:
+Coding the above being a bit tedious, [Apache Sling Servlets Annotations](https://github.com/apache/sling-org-apache-sling-servlets-annotations/) provides handy `SlingServletFilter` annotation to set those values:
 
     ...
        import org.apache.sling.servlets.annotations.SlingServletFilter;