Skip to content

Conversation

@jameskhedley
Copy link

issue #1468

@jansinger
Copy link
Contributor

The fixed DefaultRedirectResolver of Spring Security now does a strict path match as required, so that the non strict mode of the BlacklistAwareRedirectResolver does not work as expected anymore.
My suggestion would be to remove the non strict mode to comply with the security requirements, but this will break existing installations using this feature, especially those using the heart mode.

@jricher
Copy link
Member

jricher commented Mar 18, 2019

FWIW, Heart mode requires strict matching, and strict mode has been the default since 1.3.2 anyway with or without heart mode.

@jricher
Copy link
Member

jricher commented Mar 18, 2019

This pull request needs to fix the associated unit tests if it's to be included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants