Consider properly testing better auth cookie

[fringe4life]

Currently a "shape test" is performed. This is to prevent blatantly invalid cookies through. However it's more than easy to spoof and even though real validation happens at page level - among other levels - it is preferable to properly test the cookie.

The next consideration however is performance and keeping the proxy lightweight as is intended. The current testing is synchronous and ideally will remain that way or do very lightweight asynchronous work.

[fringe4life]

getCookieCache seems like the right choice for this. Seems like lightweight async work and is clearly fast based on the 3d models site

[fringe4life]

Done locally

[fringe4life]

It seems that the Boolean testing of the session cookie actually exposes a flaw in the proxy that is useful to discover. The session data isn't being refreshed so after five minutes the proxy redirects to sign in for auth routes. I actually had this issue with a react router v7 site causing auth checking issues. Eventually I fixed it by ensuring session data cookie was being refreshed on expiration

[fringe4life]

Okay server actions can't set cookies. The session data cookie is not being updated. Apparently the Elysia js mount of better auth routes may be the issue. It is certainly preferable to fix this properly

[fringe4life]

The site seems to fail proxy test after 5 minutes in development or production. May temporarily have to use getSession() lookup. To ensure session data cookie is refreshed

[fringe4life]

getSession doesn't work in proxy.ts

[fringe4life]

Could return to either detecting presence of session token cookie using bun with shape detection or make sure Elysia is forwarding set cookie to proxy

[fringe4life]

Have implemented a bun friendly version of getSessionCookie for the proxy

[fringe4life]

The response in GitHub issues apparently is to use client side getSession or useSession to ensure cookie refresh if it's undesirable to use server side getSession in the proxy