Caching issue of JSESSIONID

[Laura15]

Hello,

We have 2 instance of the website, one for users from US and one for everybody else. The difference in the urls are the parameters:

- example.webshop.com -> for all users

- example.webshop.com/us

If I open one of the pages, mentioned above and then want to switch to the other, then the content of the page won't be changed: "We're sorry, but we couldn't find the requested page. Please click to go to HomePage". 

The reason for it, that a JSESSIONID will be created by the first visit and won't be refreshed when changing the parameter in the url. After I cleanup the Cookies, I can switch to the other site. All is happening before the login.

Do you have maybe an idea, how this could be solved? 

[andyfletcher]

From what you've described it sounds like you're running the 2 CMSSites using a single storefront extension, i.e. one Tomcat web context. It will be setting the session cookie with a path of /

e.g. if you look at your response headers you'll see something like

Set-Cookie: JSESSIONID=Y1-a1a1a1a1-a1a1-a1a1-a1a1-a1a1a1a1a1a1.accstorefront-a1a1a1a1a-1aaaa; Path=/; Secure; HttpOnly; SameSite=None

That same cookie will be used for all urls on your domain below /

What you want to do is have 2 separate cookies, one of which has a path of /us However, you'll still have a problem that the way the browsers send cookies is if there isn't an existing cookie for /us it'll send the one for the next most specific path up the hierarchy, i.e. /

A way to resolve this is to run your 2 sites on /us and something else like /row (rest of world) or /all at the root just serve up an interstitial site selector (that doesn't set a JSESSIONID cookie!) or a redirect based on some geolocation technology. Have a look at the SAP default accelerator method EnhancedCookieGenerator.setEnhancedCookiePath for a place to amend the cookie path based on which CMSSite you are currently browsing.