Hotfix access token structure #264
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomasMizera
force-pushed
the
hotfix-access-token-structure
branch
from
23d5d18 to
5bf360a
Compare
Pull Request Test Coverage Report for Build 17232971781Details
💛 - Coveralls |
varmar05
approved these changes
Aug 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Access tokens do not need to start with
.. If the payload is not big enough, data do not get compressed and the dot is not prepended. See https://github.com/pallets/itsdangerous/blob/main/src/itsdangerous/url_safe.py#L55The fix is to make the
decode_token_datamethod accept tokens that do not start with dot and applyzlib.decompressonly for tokens that are compressed.