Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetty 12 - Optimize RequestLog information retrieval #8715

Open
sbordet opened this issue Oct 14, 2022 · 1 comment
Open

Jetty 12 - Optimize RequestLog information retrieval #8715

sbordet opened this issue Oct 14, 2022 · 1 comment

Comments

@sbordet
Copy link
Contributor

sbordet commented Oct 14, 2022

Jetty version(s)
12+

Enhancement Description
Following the comments in #8705, we should find a more efficient way to extract information from the current Jakarta EE request to be stored in the Jetty core request so that it is accessible to the RequestLog.
In particular, information that are specific to Jakarta EE such as the remote user, the real path and the Servlet name.

The RequestLog implementation should collaborate and expose whether it really need those information, so that if it is not needed it is not retrieved nor stored.

The ideas in #8705 are too specific to a particular implementation of RequestLog, the CustomRequestLog, but the mechanism should be generic.

@github-actions
Copy link

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Oct 15, 2023
@sbordet sbordet removed the Stale For auto-closed stale issues and pull requests label Oct 15, 2023
@gregw gregw removed the Jetty 12 label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants