You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
-
This is the gist of the known caching issue:
The page on which you sign-in (whichever page that is), when visited after you have signed-in... the browser is serving from local cache and isn't going back to the server.
Why? I do not know.
It only affects the page on which you originally click the auth0 link, and then visits after the first successful one.
So if you sign-in on / then / will always show you signed out (because it's giving you the page as it was when you were signed out).
In Chrome developer tools, one gets the cryptic message "Provisional headers are shown" but this doesn't say how to solve it.
I don't know how to force the browser to revalidate.
Velocio
correction, if i go to the forums page and it appears i am logged out, but if i then chose a forum i am logged in