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.
Documentation clarification (.remove and secure flag)
See original GitHub issueIn the specification, regarding removal of cookies (.remove), the following is specified:
IMPORTANT! when deleting a cookie, you must pass the exact same path, domain and secure attributes that were used to set the cookie, unless you're relying on the default attributes.
During my testing, it seems this is true for domain and path, but it does not seem to be true for secure. We set the cookie to secure on the server (Chrome Developer Tools confirms this), but it seems to be possible to remove the cookie without setting the secure flag. Explicitly removing with secure: false seems to work as well. Should this not work (indicating I am doing something wrong, which might entirely be the case), or am I misunderstanding the documentation?
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (10 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’ll say, you guys are quick at responding! I created a PR with
secureremoved from the text (and fixing a were -> was, sorry :p). It’s right here: https://github.com/js-cookie/js-cookie/pull/204Please let me know if I did anything wrong in the PR, I am not a very seasoned contributor to open source projects.
Thanks for the clarification!
Created a PR. See https://github.com/js-cookie/js-cookie/pull/369.