Fix BadSignature exception handling in SessionMiddleware #1264
+15
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
SessionMiddleware
does not catch all possible exceptions ofTimestampSigner.unsign
, specifically there is an edge case where aBadSignature
exception can be raised by the method if a totally bogus session cookie is provided that does not match the expected format.This PR broadens the caught exceptions (since all the other exceptions inherit
BadSignature
) and fixes the issue.The issue can be reproduced by running the new test without the fix applied.