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 am working on porting a website into Electron and am using js cookie to set and get cookies. Js cookie lets me set a path, since the web page isn't at site.com/ to prevent cookie naming conflicts between apps. This still allows me to writethe cookies to the correct paths in localStorage, but it's not able to read the cookies back when I go to reload the page.
I was wondering if it would be worthwhile to allow the user to set a path to read cookies from. I'd really like to leave the javascript from the website intact with no changes, and so far it's been going well aside from the inability to read the cookies I've set.
The text was updated successfully, but these errors were encountered:
Hey @GammaGames – sorry for not responding sooner, this should totally be possible since Tough Cookie (the backing library) supports it.
I'm not sure when or if I'll have time to put work in on this, but I'll give it a try. If you have a PR, feel free to @ mention me, and I'll take a look.
I am working on porting a website into Electron and am using js cookie to set and get cookies. Js cookie lets me set a path, since the web page isn't at
site.com/
to prevent cookie naming conflicts between apps. This still allows me to writethe cookies to the correct paths in localStorage, but it's not able to read the cookies back when I go to reload the page.I was wondering if it would be worthwhile to allow the user to set a path to read cookies from. I'd really like to leave the javascript from the website intact with no changes, and so far it's been going well aside from the inability to read the cookies I've set.
The text was updated successfully, but these errors were encountered: