-
-
Notifications
You must be signed in to change notification settings - Fork 596
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
Support token compression #82
Comments
/cc @DASPRiD |
After discussing this with @lcobucci, we came to the conclusion that compressing tokens is just not worth it. Specifically, for following reasons:
Therefore, I'm closing this as "won't fix", as it really doesn't need a fix. |
There is one use case not considered: copy/pasting JWT. That's needed when JWT is generated on the web and human has to copy it to a local terminal, bootstrapping their client that talks to the server. There could be another variation of the token so that compression wouldn't be part of the header. Compression probably doesn't have to be adaptive, since there's not much to choose from. However, there is a challenge how to compress small-sized JSON into ASCII representation. |
JWT tokens can be quite long: adding some basic gzip (or better) support to compress their contents/signature would be a plus.
Doesn't seem like it's part of the spec for now, though: dgrijalva/jwt-go#102 (comment)
Maybe a good idea to push back to the spec here?
The text was updated successfully, but these errors were encountered: