[sling-site] branch master updated: Add documentation about disabling filter

[ro...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rombert 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 99b9cf8  Add documentation about disabling filter
99b9cf8 is described below

commit 99b9cf8549a9516004ddd856cfc25e0e2eb681f6
Author: Robert Munteanu <ro...@apache.org>
AuthorDate: Wed Jun 6 23:43:18 2018 +0300

    Add documentation about disabling filter
---
 src/main/jbake/content/documentation/the-sling-engine/filters.md | 4 ++++
 1 file changed, 4 insertions(+)

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 c172e1f..4d30073 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/filters.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/filters.md
@@ -67,6 +67,10 @@ When a servlet or script is including or forwarding to another resource for proc
 
 As a consequence, request level filters will be called at most once during request processing (they may not be called at all if a filter earlier in the filter chain decides to terminate the request) while the component level, include, and forward filters may be called multiple times while processing a request.
 
+## Disabling Filters
+
+As hinted earlier in the page, a filter is ignored if you set an invalid `sling.filter.scope`. To disable a specific filter, you can deploy an OSGi config setting an invalid `sling.filter.scope`, for instance _disabled_.
+
 ## Troubleshooting
 Apart form the logs which tell you when filters are executed, two Sling plugins provide information about filters in the OSGi console.
 

-- 
To stop receiving notification emails like this one, please contact
rombert@apache.org.