redis is not working with safari using Atlassian Connect Addon (ACE)

[Lutz Bliska]

We are still on the same story as described here: https://answers.atlassian.com/questions/50367209 

As @James Hazelwood told us, we did setup the caching service redis (connect-redis).

The service works fine with FF and chrome but it fails with safari. 

It seems that the session variables are getting lost after routing.

1. loading the addon using default route (setup in the descriptor-file) and set an session variable. the session output looks like this:
   
   

   Session {
     cookie: 
      { path: '/',
        _expires: 2017-02-24T17:11:21.686Z,
        originalMaxAge: 1800000,
        httpOnly: true,
        secure: true },
     URL: 'https://myurl.com/' }

2. posting a Form to a other route (/login) the session looks like that:

   Session {
     cookie: 
      { path: '/',
        _expires: 2017-02-24T17:11:21.343Z,
        originalMaxAge: 1800000,
        httpOnly: true,
        secure: true } }

The session variable URL gets lost.

Any ideas why ?

Thank you for your support

[Robert Massaioli _Atlassian_]

I answered this question here: https://answers.atlassian.com/questions/57001131

[James Hazelwood]

Ah, sorry to hear you had trouble with posting the question - no worries.

As I said, I'm not too familiar with how session variables work in ACE but I think that's quite a likely hypothesis - Safari is probably handling or restricting cookies slightly differently.

[Lutz Bliska]

Hi @James Hazelwood. I'm sorry about the duplicate, i've delete them. It wasn't easy to ask this question in Atlassian Answers because it fails several times... timeout exception e.g.

Okay, but this is not our topic at the moment. 

I'm using a postgres database to store data persistent, but i need temporary session data, which can be "deleted" when the user is logged out. The funny part is that only safari browser have problem with this session. May it depends on cookie-storage from a cross-domain / iframe ? 

The session and it's variables will be only destroyed/ reset when the user is logging out.

Any advise ?

Thank you

[James Hazelwood]

In any case, I'm afraid I don't know much about connect-redis, the "connect" in the name is just a coincidence. If I had to guess, perhaps doing a redirect to the login page is causing the session variable to be reset? Hopefully somebody else on Atlassian Answers has experience with this library or with Redis session management in general.

If you want something longer lived, you can store whatever it is you want to store against the user / host combination rather than against an ephemeral session.

[James Hazelwood]

Hi Lutz,

There appear to be two duplicates of this question... which one should we reply to?