We are still at the same project at described here: https://answers.atlassian.com/questions/50367209
As @James Hazelwood suggest us, we did setup the cache service redis (connect-redis).
Redis works fine with FF and Chrome Browser but it doesn't work with safari.
The problem is that the session vars are getting lost after the first route.
e.g.:
request to the default endpoint (configured in the atlassian-connect.json) and the session looks like this:
Session { cookie: { path: '/', _expires: 2017-02-24T17:11:21.686Z, originalMaxAge: 1800000, httpOnly: true, secure: true }, URL: 'https://test.net' }
After posting a from to a other endpoint (/login) the session object looks like that:
Session { cookie: { path: '/', _expires: 2017-02-24T17:11:21.343Z, originalMaxAge: 1800000, httpOnly: true, secure: true } }
So the variable URL gets lost.
Any ideas why ?
Thank you for your support
Community moderators have prevented the ability to post new answers.
I believe that using Cookies inside iFrames for Safari is notoriously hard. This explains the issue briefly: https://github.com/vitr/safari-cookie-in-iframe
I would recommend storing your state with the page in another manner. Otherwise you should be able to find workarounds for this issue. Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.