Configure the session domain and cookie path

Reset a session

To completely clear out a Foxy session:

FC.session.reset();

Set the session domain

sitedomain controls which domain the fcsid cookie is set on. By default, if your domain is passed in as example.com or www.example.com, the cookie is set at the second-level domain — .example.com. For a third-level domain like subdomain.example.com, the cookie is set at .subdomain.example.com.

Set it inside FC.onLoad:

var FC = {
  onLoad: function () {
    FC.settings.sitedomain = 'store1.example.com';
  }
}

This matters if your site isn’t at the second-level domain, or if you want to isolate sessions by subdomain — for example, if you run separate Foxy stores at donations.example.com and products.example.com and don’t want their sessions to overlap, or if your site is hosted at a third-party domain like example.squarespace.com and you don’t want your session shared across every site on that domain.

Set the cookie path

cookiepath controls the path the fcsid cookie is set on. This is normally left empty, but you can use it to run multiple isolated Foxy sessions on the same domain — for example, splitting an English store at /en/ from a Spanish store at /es/.

var FC = {
  onLoad: function () {
    FC.settings.cookiepath = '/donations/';
  }
}

Notes

• The www subdomain is effectively ignored when counting domain levels. To lock sessions down to www.example.com specifically, set sitedomain to something like www1.example.com — the actual value doesn’t matter, only the number of dots after www is stripped.

• If you isolate sessions by subdomain, Foxy’s JavaScript can’t also be loaded at a parent domain. For example, with separate stores at products.example.com and donations.example.com, you can’t also load Foxy at www.example.com or example.com — that would set the session cookie at .example.com and override both subdomain sessions.

• cookiepath must start and end with a /, or you may run into issues (especially in older browsers).

• If splitting sessions by path, the trailing slash is critical — example.com/bookstore/ and example.com/donations/ work, but example.com/bookstore and example.com/donations (without trailing slashes) will collide.

• sitedomain and cookiepath are set on FC.settings inside FC.onLoad, not with FC.override — see Configure JavaScript loading options for the override pattern used elsewhere.