TYPO3 Core

Hi Markus,

@public function set($key, $value) {
$this->getFrontendUser()->setKey('ses', $this->prefixKey.$key, $value);
$this->getFrontendUser()->storeSessionData();
}@

this is my function to store data. $this->getFrontendUser() just returns $GLOBALS['TSFE']->fe_user; From what i see setAndSaveSessionData() is just a shortcut for this 2 actions. This doesn't work for me - there is always new id/hash generted as $this->isExistingSessionRecord($id) in mentioned condition will always return false; For test i removed this from IF statement and than my session data is fetched as it should.

I do not know how exactly the session handling works here (would have to investigate whole code) but what i want to know now is does the entry should be created in fe_sessions table not only for existing and logged in user but also for simple visitors?

Marcin Sągol wrote:

I do not know how exactly the session handling works here (would have to investigate whole code) but what i want to know now is does the entry should be created in fe_sessions table not only for existing and logged in user but also for simple visitors?

fe_sessions is only used for login of FE user, not for storage of the session data (in contrast to BE); all session data of FE users, regardless of login or anonymous session, is stored in fe_session_data

Thorsten ok thank you for the explanation. My question is why then isExistingSessionRecord() checks fe_session and based on that is generated session id/hash for simple visitor? Or am im getting it wrong?

Method isExistingSessionRecord() is overwritten in \TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication: if the parent method doesn't return a result from fe_sessions, fe_session_data is checked.

From what i see fe_typo_user cookie is not set after i cleard all of them to do more test. Is it required for proper session data handling ?

Any ideas why it can;t be set? If i login with some fe_user account the cookie is created but not for guests.

If the website is behind an HTTP proxy, Varnish or something similar - then this might be the reason for the fe_typo_user cookie not being forwarded and set at the client browser.

Thanks Oliver for the good suggestion. The problem was behind Varnish configuration. After small modifications all seems to work. Sorry for taking your time and thanks again all of you.

This issue can be closed.

@Thorsten Kahler: Why are you setting this to rejected?? Did we reject something?
I guess we can "close" this issue.

Small info: when i was changing default Varnish configuration to work with TYPO3, i commmented this part:

sub vcl_fetch {
     if (beresp.ttl <= 0s ||
         beresp.http.Set-Cookie ||
         beresp.http.Vary == "*") {
                /*
                 * Mark as "Hit-For-Pass" for the next 2 minutes
                 */
                set beresp.ttl = 120 s;
                return (hit_for_pass);
     }
     return (deliver);
}

With this configuration back all works fine.

Markus Klein wrote:

@Thorsten Kahler: Why are you setting this to rejected?? Did we reject something?
I guess we can "close" this issue.

IMHO it's easier to distinguish solved issues (which had an impact on the code base) from those that were sorted out by discussion. The request to change the code has been rejected by the author himself.