You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was following your tutorial from youtube it works fine,
You explained it very well, thank you for that.
I just have a little query why do we need to prefix 'JWT ' to token while sending a response back.
By the way with prefixing 'JWT ' it works fine but as soon as I remove 'JWT ', it didn't work, I'm wondering why this is happening? any specific logical or syntactical reason?
The text was updated successfully, but these errors were encountered:
Maybe
JWT defines a special structure of information that is sent over the network. It comes in two forms, serialized and deserialized. The former is used directly to transmit data with requests and responses. On the other hand, to read and write information to a token, it needs to be deserialized.
Also because JWT is one of the most common methods of authentication for requests to Java WEB applications and this type of protection and authentication has several advantages:
convenience (no need to pass login and password with every request);
less queries to the database (the token may contain basic information about the user);
easy implementation (it's enough to use a ready-made library to generate and decrypt a token)
Hello,
I was following your tutorial from youtube it works fine,
You explained it very well, thank you for that.
I just have a little query why do we need to prefix 'JWT ' to token while sending a response back.
By the way with prefixing 'JWT ' it works fine but as soon as I remove 'JWT ', it didn't work, I'm wondering why this is happening? any specific logical or syntactical reason?
The text was updated successfully, but these errors were encountered: