-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Expose TLS protocol used for connection in SecureRequestCustomizer #85
Comments
I think the best way to do this is to expose the |
+1 to what @sbordet said.... but make it optional. Perhaps in the style of ForwardedRequestCustomizer, have a setSslSessionAttribute(String) method that set's the name of the attribute to use. If not set, then the attribute is not set. |
Seems a bit dangerous to expose the full SSLSession to the web applications. Why is just exposing the TLS protocol in a new attribute undesired? |
Dangerous, how ? Exposing the TLS protocol would be a non-standard addition, and then we would need to expose a bunch of other information that may be needed to web applications. Exposing the |
If you don't know what you are doing with the SSLSession, couldn't you cause problems with your connection easily? |
People can always mess things up if they don't know what they're doing, e.g. call For people that needs particular, non-common, |
Fixed in jetty-9.2.x and merged up to jetty-9.3.x |
…ustomizer. Exposed the SSLSession as attribute only if the attribute key is valid.
This is an enhancement request to include the TLS protocol that was used to establish the connection in the request attributes that SecureRequestCustomizer uses.
This enhancement request is for Jetty 9.2.x +
The text was updated successfully, but these errors were encountered: