On 24/09/2021 19:03, Christopher Schultz wrote:
Mark,
I haven't looked at the patch yet but I was thinking about this since
you mentioned it at ApacheCon.
Many load-balancers and other similar network systems are capable of
generating their own request-identifiers and sending them as request
headers to origin servers. I think it would make sense to allow the user
to either use a container-generated request identifier (as you have
implemented it) or to allow a (trusted) upstream component to provide
one to the container.
WDYT?
I don't think that covers all use cases as it requires the successful
parsing of the incoming request.
Users are free to log multiple IDs from different sources if that makes
sense for their environment. These IDs are primarily to fill the gap
that there wasn't IDs from the container perspective.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
