Comment 5 for bug 1939162

During testing I found that if you haven't caused the 'ses' cookie to be set the clear cache action will be redirected to the login page. This also returns a 200 and is seen as successful, even though nothing is done. It looks like WWW/AccessHandler.pm might be one of the last places we're not considering both possible cookie names.

Here's a branch that signs off on Galen's commit and adds another to use the newer cookie: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1939162_clear_cache_signoff / working/user/jboyer/lp1939162_clear_cache_signoff