$.cookie() should default path to '/' about jquery-cookie HOT 19 CLOSED

This is just the way how cookies work in any browser by default. I am reluctant to change that behavior.

from jquery-cookie.

I.e. I am reluctant to change any behavior in such fundamental way. It's too obtrusive.

from jquery-cookie.

let's at least add this to the documentation.

from jquery-cookie.

I'm totally agree with ssoroka. I was facing the same problem til I read these comments. Add this to the documentation, please.

from jquery-cookie.

I was also completely fooled by this. Hours of debugging. To help others out, maybe you could add some text to your README or make it more clear in the documentation.

If you don't know how (stupid) cookies actually works, it's really hard to know what's wrong.

Cheers.

from jquery-cookie.

I will add that to the README. Though I am nearly convinced that path = '/' should become default.

from jquery-cookie.

So you changed opinion on that? I think it's a great idea. Think about the updaters, though. They may need some info on that, since it's an "API change".

from jquery-cookie.

I just spent 2 hours on a problem linked to that default path not being '/' thing...

from jquery-cookie.

The issue I still have with having a default path is that when one wants the behavior as is, you would have to pass null, which to me at least feels not intuitive at all:

$.cookie('foo', 'bar', { path: null }); // null denotes current path?

That said, I am planning to document that behavior prominently and provide a way to define defaults, so that a developer can easily turn on '/' as the default path with a single line of code. That way it'll also not break existing code.

// bulk
$.cookie.defaults = { path: '/', expires: 365 };

// single
$.cookie.defaults.path = '/';

from jquery-cookie.

I'm encountering the path issue as well. Although I am setting it so that it should only be /, but it's still saving a subdirectory if changed at that location. How can it be forced to only use tld?
I'm using the version you've got hosted here, with FF3.6.13 JQ1.4.4 and the line of code is
$.cookie("myCookie", "0", { expires:7 }, { path: '/', domain: "local.mysite.test" });
if saved at local.mysite.test/somepath it's saving the cookie path as 'local.mysite.test/somepath' instead of the tld.

from jquery-cookie.

You're using it wrong, options are a single argument.

$.cookie("myCookie", "0", { expires:7, path: '/', domain: "local.mysite.test" })

from jquery-cookie.

So I was. Thanks for the reply carhartl.

from jquery-cookie.

'global' path cookie again.

I set cookies path to '/'
but I had a problem to get this global values

if I get values from standart options: $.cookie('variable') i will get values from this page (NOT path: '/').

but logging $.cookie() object show me the really {path : '/'} values and this show me how get cookie values with my params (such a {path : '/'})

$.cookie().variable

if($.cookie().variable == 1)
{
console.debug('yes, you do this!');
}

Of course I was talking about the pages with the root directory other than '/'
browser chrome

from jquery-cookie.

I believe in your case a cookie with a path for a particular page (in case of an omitted path, the "current" page) may shadow a cookie with the same name "higher up" in the path hierarchy.

What happens if you start with a blank page, e.g. clean all cookies?

from jquery-cookie.

yes, indeed.

Thanks for the explanation. I thought that I had them cleaned.
sorry for inconvenience caused.

And thank you for this plugin!

from jquery-cookie.

I'm here because I too was caught unaware by this behavior.

from jquery-cookie.

@brycenesbitt but now this is properly documented at https://github.com/carhartl/jquery-cookie#path

from jquery-cookie.

weird default path messed me up

from jquery-cookie.

@FagnerMartinsBrack thanks much better. Having it in the example as 'Create expiring cookie, valid across entire site:' is particularly nice, since that's where the lazy will look.

from jquery-cookie.