Good point, thanks. In my test the page made one getSession() call and the proxy made another, so cache() wouldn't have changed the 4, but it matters as soon as a layout and a page (or a few server components) each check the session in the same render, since each call would otherwise cost 2 queries on Prisma 7. And yes, the proxy can't share that cache, which is one more reason to keep it as an optimistic redirect and do the real check in the page.