Pages that require authentication sometimes allow browser to cache redirect to login page

In some cases we (our code, or APO) set a max-age of 14400 on the 302 redirect to the login page. This results in users not being able to log in, since they keep being sent to the login page.

I noticed the cached redirect after receiving a .har file with the request logs from a user that experienced the issue (see attached screenshot which shows the 302 after a successful login attempt).