11
Ability To Reduce Cookie Size by Excluding Metadata
Source: supabase/supabase#29782 · opened by @J43fura
Ability To Reduce Cookie Size by Excluding Metadata Summary: I would like to request the ability of a reduction in the cookie size for Supabase Auth by excluding metadata from being stored in the cookie. By default, Supabase Auth currently stores metadata in the session cookie, leading to larger cookie sizes that can negatively impact performance & user experience, especially in environments where cookie size limits are a concern. Motivation: 1. Compliance with Cookie Size Limits: Many web browsers and reverse proxies impose strict limits on cookie sizes (often around 8KB). Exceeding this limit can lead to unexpected behaviors, including rejection of cookies (python-websockets, Nuxt, Cloudflare...) causing 431 Request Header Fields Too Large issues. 2. Better Developer Control: Allowing developers to disable the storing of metadata in the cookie if necessary will give developers better control over the size and contents of the authentication cookies. Proposed Solu…
No pledges yet. Be the first to back this.
Comments
Similar requests
Enable Supabase SSR cookies with Vike Cloudflare
1 vote · 0 comments
Sign in methods should all support adding user metadata
12 votes · 0 comments
supabase/ssr: Offer other means of storing/sending session data other than cookies
3 votes · 0 comments
Simple idea to sync client and server (cookie) access token
3 votes · 0 comments
Error 502 with Supabase client when using Nginx as a reverse proxy
19 votes · 0 comments
No comments yet.