The condition of a non-existent login token can happen for concurrent requests. Admins can not do anything about this. So this is to be expected to happen occasionally. This event is only bad if none of the requests is able to re-acquire a session. Luckily this happens rarely. If a login loop persists an admin can still lower the log level to find this info. But a default error log level will no longer write those infos about the failed cookie login of one request. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at> |
1 年之前 | |
---|---|---|
.. | ||
Listeners | Fix avatar cleanup on user delete | 1 年之前 |
Backend.php | Update php licenses | 3 年之前 |
Database.php | Fix creation of new user and display the correct error message | 1 年之前 |
DisplayNameCache.php | Make DisplayNameCache return null if user doesn't exists | 1 年之前 |
LazyUser.php | Make DisplayNameCache return null if user doesn't exists | 1 年之前 |
LoginException.php | Update php licenses | 3 年之前 |
Manager.php | LDAP to no register new users when outside of fair use or over limits | 1 年之前 |
NoUserException.php | Update php licenses | 3 年之前 |
Session.php | Fix unsuccessful token login logged as error | 1 年之前 |
User.php | Merge pull request #33793 from nextcloud/fix/noid/rtrim-cloud-id | 1 年之前 |