-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Token created/compressed with 0.10.6 can't be parsed with 0.10.7 #536
Comments
Hi there - thanks for the issue! Do you know if this has anything to do with the fact that the test JWT is not signed? Have you tried it with a signed JWT between 0.10.6 and 0.10.7? Just curious... |
Hi, the issue also happens with signed tokens - I just narrowed the reproducer down to the most simple case. |
Related question: would you recommend ZIP compression over DEF? Since clients of our token server might use older versions we need tokens to be stable across versions... |
@lkoe I don't have a particular recommendation really - my assumption is gzip is pretty-well ubiquitous so I'd probably default to that in my own projects, but that's just a personal preference - not something I can 'formally' recommend (if that makes sense). Cheers! |
…ation if encountering an IOException. This allows compressed JWTs created before 0.10.7 to still work. Fixes #536
P.S. even though this is a backwards compatible fix, those using DEFLATE on 0.10.6 should upgrade to 0.10.7 or 0.10.8 as soon as we release it to avoid the memory leak in DEFLATE <= 0.10.6. |
Thanks @lhazlewood much appreciated! |
Simple testcase:
Fails currently with:
The text was updated successfully, but these errors were encountered: