The authenticator should not redirect in the case of an ajax request

This works fine, but, as discussed on the chats when the fix was proposed, the identification of the Ajax requests needs to be improved.

One example of such a request (that is an ajax but not identified as such) is the lock request that takes place when editing a page with the inplace edit mode (default edit mode when you click on the edit button). The way that works is that it sends a request to lock the page first and then it loads the edit mode "in place". If session is expired, the lock request still results in a 302, even after applying this fix.

Thomas Mortagne I'll let you decide where the ajax detection improvement should be reported and fixed. Thanks!