mirror of
https://github.com/jcreek/LivingDexTracker.git
synced 2026-09-14 17:42:17 +00:00
b7d2db4959
@supabase/ssr 0.1.0 never removed the old unchunked session cookie once a refreshed session grew past one cookie, and always read that stale copy first. Every load then retried an already-used refresh token, which the hosted auth server rejects, signing the user out. Upgrade @supabase/ssr to 0.12 (and supabase-js to match) and move to the getAll/setAll cookie API, which clears stale chunks when writing.
48 lines
1.5 KiB
TypeScript
48 lines
1.5 KiB
TypeScript
import { PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY } from '$env/static/public';
|
|
import { createServerClient } from '@supabase/ssr';
|
|
import type { Handle } from '@sveltejs/kit';
|
|
|
|
export const handle: Handle = async ({ event, resolve }) => {
|
|
event.locals.supabase = createServerClient(PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY, {
|
|
cookies: {
|
|
getAll: () => event.cookies.getAll(),
|
|
/**
|
|
* Note: You have to add the `path` variable to the set method due to sveltekit's cookie
|
|
* API requiring this to be set, setting the path to '/' will replicate previous/standard
|
|
* behaviour (https://kit.svelte.dev/docs/types#public-types-cookies)
|
|
*/
|
|
setAll: (cookiesToSet) => {
|
|
cookiesToSet.forEach(({ name, value, options }) => {
|
|
event.cookies.set(name, value, { ...options, path: '/' });
|
|
});
|
|
}
|
|
}
|
|
});
|
|
|
|
/**
|
|
* Unlike `supabase.auth.getSession`, which is unsafe on the server because it
|
|
* doesn't validate the JWT, this function validates the JWT by first calling
|
|
* `getUser` and aborts early if the JWT signature is invalid.
|
|
*/
|
|
event.locals.safeGetSession = async () => {
|
|
const {
|
|
data: { user },
|
|
error
|
|
} = await event.locals.supabase.auth.getUser();
|
|
if (error) {
|
|
return { session: null, user: null };
|
|
}
|
|
|
|
const {
|
|
data: { session }
|
|
} = await event.locals.supabase.auth.getSession();
|
|
return { session, user };
|
|
};
|
|
|
|
return resolve(event, {
|
|
filterSerializedResponseHeaders(name) {
|
|
return name === 'content-range';
|
|
}
|
|
});
|
|
};
|