[
https://issues.apache.org/jira/browse/SLING-12406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872931#comment-17872931
]
Robert Munteanu commented on SLING-12406:
-----------------------------------------
This is a change which has far-reaching impact. I think the alternative is to
configure the request logging to include those headers, rather than changing
the log format.
https://sling.apache.org/documentation/development/client-request-logging.html#log-format-specification
While I haven't seen tools and processes that depend on the thread name, I am
100% sure that this will cause confusion if implemented.
> thread name should be set to x-request-id
> -----------------------------------------
>
> Key: SLING-12406
> URL: https://issues.apache.org/jira/browse/SLING-12406
> Project: Sling
> Issue Type: Improvement
> Components: Authentication
> Reporter: Patrique Legault
> Priority: Major
>
> The request in sling request log is not logged if authentication has failed,
> the only thing you have left to review is the error log.
>
> If the use of a x-request-id is present the thread name should be set to that
> so that we can trace the request in the log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
