[Flow] Strange Issues with sessions and ACLs

Christian Loock chl at vkf-renzel.de
Mon Sep 23 09:53:26 CEST 2013


Am 19.09.2013 10:10, schrieb Christian Loock:
> #1: Notice: unserialize() [<a 
> href='function.unserialize'>function.unserialize</a>]: Error at offset 
> 5337 of 5396 bytes in 
> /home/www/flow_vkf_search_chl/Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Cache/Frontend/VariableFrontend.php 
> line 86 
So we investigated further in this matter:

When not being logged in and trying to call a controler action that is 
being protected by ACL, Flow intercepts the requests and forwards to the 
login. Here it starts a new session, when 
securityContext->setInterceptedRequest is called. (this happens before 
the redirect).

Right after the redirect to the login action (which is the original 
login action, called inside a derived controller) it tries to read 
session data from the cache. This leads to the above unserialize error. 
We tried to look into the cache file at the erroneuos offset it 
complains about, but couldnt really find any obvious errors...

This error right now has to be considered critical, but don't really 
know where to look further.

Any help or usefull hint would be highly appreciated, since we are 
shortly before releasing the first version of our application.

Thanks a lot,

Christian


More information about the Flow mailing list