-
Notifications
You must be signed in to change notification settings - Fork 381
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
signature is invalid #281
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I am use jwt-go to do my authentication. Everything seems fine unitl today I find a strage phenomenon.
I use curl to do the PUT request twice with the exact request parameters. But the first request was rejected by jwt. and the second one succeed. As you can see the above screen is the actual log of my server. The first request came with nothing
I have walked through the source code of jwt-go, and wonder if there are some data race of the verify logic
as you can see, the second request is blocked to sending the actual data to the server, while the first one just return quickly
I use HS512 as my jwt signing and verifying algorithm
The gin-jwt version I use is 2.6.4
The text was updated successfully, but these errors were encountered: