Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sometimes $cookies.set is not consistent with `document.cookie=`
See original GitHub issueWhen we use document.cookie='email=lifubang@acmcoder.com', the value of document.cookie is email=lifubang@acmcoder.com;
But when we use this.$cookies.set('email', 'lifubang@acmcoder.com'), the value of document.cookie is email=lifubang%40acmcoder.com.
It’s ok when we just use cookie in front-end, but the back-end will get an inconsistent cookie value when we use vue-cookies to replace document.cookie= in front-end, it would cause the back-end to upgrade their code.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree with @lifubang in that I am having issues with this as well.
I don’t mind if the value is encoded in the cookie storage, but the decode does not work for me when I get cookies back. When I use Vue.$cookies.get() it returns the escaped strings for me, so the functionality is ruined.
My understanding is that the cookie stores a standard string and handles all required escaping itself as well.
当cookie含有 ASCII 特殊符号时，encodeURIComponent会对key or value 进行编码，这样会导致接下来的请求后端cookies校验无法通过，希望不要对@&=+$#这些特殊符号进行编译。