Skip to content

Conversation

@lachlan-roberts
Copy link
Contributor

Closes #12720

Currently SecurityHandler does only Response.writeError when a 403 response needs to be sent. However this will not dispatch to a servlet error page, for this we need to do AuthenticationState.writeError and handle the case if it returns AuthenticationState.ServeAs.

@gregw
Copy link
Contributor

gregw commented Oct 13, 2025

@lachlan-roberts the CI failures look to be more than flakes.

Copy link
Contributor

@gregw gregw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

more than flakes

@lachlan-roberts
Copy link
Contributor Author

@gregw the tests are failing because the AuthenticationState.writeError and ErrorHandler.writeError do not support taking a message string.

So do you think i should adjust both the AuthenticationState.writeError and ErrorHandler.writeError API to take a String message, or should I adjust the tests to not check for the !authroized string?

@joakime joakime moved this to 👀 In review in Jetty 12.1.4 Oct 16, 2025
@lachlan-roberts lachlan-roberts requested a review from gregw October 20, 2025 23:33
Signed-off-by: Lachlan Roberts <[email protected]>
@lachlan-roberts lachlan-roberts requested a review from gregw October 21, 2025 00:19
Signed-off-by: Lachlan Roberts <[email protected]>
@lachlan-roberts lachlan-roberts requested a review from gregw October 29, 2025 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

Error attributes not set on request in Jetty 12

3 participants