Hydration mismatch warning when login state changes

[jarkt]

I get some warnings about hydration mismatches under special circumstances.

1. User requests /protectedResource, gets a HTTP 401 and sees the login form
2. User enters credentials, continues on the same path and sees the protected resource
3. User navigates away and back to /protectedResource 💥

At this point the hydration mismatch warning appears, because the route is now rendering the protected resource instead of the login form.
Everything works fine and the warning is expected under these circumstances. What can I do to get rid of the warnings?

I'm wondering why the check doesn't just run once after the initial page load.