[TYPO3-core] RFC #0013938: Backend session is locked to useragent

[Ernesto Baschny [cron IT]]

Stefan Galinski schrieb am 19.01.2011 19:25:
> Ernesto Baschny [cron IT] wrote:
> 
>> Dmitry Dulepov schrieb am 19.01.2011 18:52:
>>> Hi!
>>>
>>> Ernesto Baschny [cron IT] wrote:
>>>> It is more like a new feature, because the useragent locking was never
>>>> configurable for the BE before. We don't want to introduce new features
>>>> (or configuration options) in older releases, do we?
>>>
>>> What about removing user agent from hash? It always log out clients.
>>> They can't work with Backend.
>>
>> I must confess I never heard this complaint. Why do user agent change
>> from one call to the next on on your clients? This isn't supposed to
>> happen?
>>
> 
> Hi Ernesto,
> 
> Just want to note that often extensions/plugins for the browser causing this 
> problems. I had login problems after I switched to Chrome, because of a 
> single plugin. The search for a fix for this issue was just annoying, 
> because you don't think in the first moment that this can be caused thru a 
> bad-written browser plugin.

Yes, maybe a solution would be throw an exception in this case ("User
agent doesn't match your session") instead of just showing the login
screen again. Because there are several reasons why a session might
become "invalid".

Then at least the user will be able to report a more precise bug report
or know the reason why he was logged off.

Cheers,
Ernesto