-
Notifications
You must be signed in to change notification settings - Fork 1
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
Allow custom strategy for handling invalid cookies #1
Comments
Thanks for your report. I think this addition seems reasonable and I will try to include this. |
mvitz
added a commit
that referenced
this issue
Jul 11, 2018
This feature allows to customize the behaviour of what should be done in case the cookie could not be verified. By default the cookie is silently ignored, as before. Closes #1
mvitz
added a commit
that referenced
this issue
Jul 11, 2018
This feature allows to customise the behaviour of what should be done in case the cookie can not be verified. By default the cookie is silently ignored, as before. Closes #1
@cstettler I prepared this feature in #2. It would be nice if you could take a look and give some feedback. |
mvitz
added a commit
that referenced
this issue
Nov 7, 2019
This feature allows to customise the behaviour of what should be done in case the cookie can not be verified. By default the cookie is silently ignored, as before. Closes #1
mvitz
added a commit
that referenced
this issue
Apr 11, 2020
This feature allows to customise the behaviour of what should be done in case the cookie can not be verified. By default the cookie is silently ignored, as before. Closes #1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if a cookie cannot be decoded due to an invalid signature, the flash manager implementation returns null:
spring-cookie/src/main/java/com/innoq/spring/cookie/flash/CookieFlashMapManager.java
Line 99 in 78e8280
In some cases, instead of simply ignoring the invalid cookie, a custom behaviour should be triggered (e.g. throwing an exception).
The text was updated successfully, but these errors were encountered: