cookie stored in the browser? Cookie and token, why only hijack the former?
cookie stored in the browser? Cookie and token, why only hijack the former?
inexplicable problem, hijacking should be any network transmission of key information or tokens, the name is just a representative.
if, specifically, token is also stored in cookies, you can simply understand that cookies is a map of the browser that can store all kinds of kv data
cookie is the wallet, and
token is the credit card in the wallet.
Previous: [resolved] the problem that custom directories cannot be copied in vue-cli3 custom preset
Next: Please tell me how to dynamically control initialRouteName in react-navigation components.