GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
No description provided.
I couldn't find a valid way of making the Exception catching cloak possible misconfiguration but I wonder if it wouldn't be better to make session serializers re-raise a common DeserializationError and catch it here.
My justification is that we are catching Exception in similar places of other cache backends. If it ends up hiding actual problems, maybe a solution could be to add debug logging.
I think debug logging would be fine here.
Are you okay to defer it until someone reports an actual problem? Also, I question the usefulness of adding more logging until we change Django's default logging config so logged statements are actually displayed somewhere.
Fixed #24468 -- Made signed cookies cache backend resilient to unpick…