[sling-site] branch clarify-client-request-logging created (now 455752670)

[kw...@apache.org]

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

kwin pushed a change to branch clarify-client-request-logging
in repository https://gitbox.apache.org/repos/asf/sling-site.git


      at 455752670 Clarify limitations on request logging

This branch includes the following new commits:

     new 455752670 Clarify limitations on request logging

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[sling-site] 01/01: Clarify limitations on request logging

[kw...@apache.org]

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

kwin pushed a commit to branch clarify-client-request-logging
in repository https://gitbox.apache.org/repos/asf/sling-site.git

commit 45575267044ae903822028f8a0fb15c817b762e4
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Tue May 16 16:46:33 2023 +0200

    Clarify limitations on request logging
---
 .../jbake/content/documentation/development/client-request-logging.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/main/jbake/content/documentation/development/client-request-logging.md b/src/main/jbake/content/documentation/development/client-request-logging.md
index 2f05c54e9..8f73f7190 100644
--- a/src/main/jbake/content/documentation/development/client-request-logging.md
+++ b/src/main/jbake/content/documentation/development/client-request-logging.md
@@ -6,6 +6,8 @@ tags=requests,operations,logging
 
 Sling provides extensive support to log various information at the before and after processing client requests. Out of the box, there are two loggers configured to write traditional `access.log` and `request.log` files. In addition more logging can be configured by providing OSGi Configuration Admin configuration.
 
+Although this request logging is implemented in a Servlet Filter for OSGi HTTP Whiteboard, this filter is bound to the Sling Servlet Context Helper and therefore only ever logs requests which are answered by the Sling Main servlet (but not requests targetting any servlets leveraging another Servlet Context Helper). Also due to the request processing order outlined in [OSGi HTTP Whiteboard Chapter 140.2.5 Security Handling](https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.http. [...]
+
 ## Traditional access.log and request.log Files
 
 In the Web Console configure the *Apache Sling Request Logger* (PID=`org.apache.sling.engine.impl.log.RequestLogger`) configuration.
@@ -52,7 +54,7 @@ In the Sling Web Console locate the Configuration page (`/system/console/configM
 
 #### Log Format Specification
 
-The log format specification generally follows the [definition of the `format` argument for the `LogFormat` and `CustomLog` directives of Apache httpd](http://httpd.apache.org/docs/current/mod/mod_log_config.html). Please see the below table for details and exceptions.
+The log format specification generally follows the [definition of the `format` argument for the `LogFormat` and `CustomLog` directives of Apache httpd](https://httpd.apache.org/docs/current/mod/mod_log_config.html). Please see the below table for details and exceptions.
 
 The characteristics of the request itself are logged by placing "%" directives in the format string, which are replaced in the log file by the values as follows: