You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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 Solution:
Optional disable: Provide a configuration option for developers to disable metadata storage in cookies if needed.
Additional Considerations:
For applications that require metadata, developers could access it securely from the server side or via API calls instead of storing it in cookies.
Thank you for considering this request! Reducing the default cookie size and providing flexibility to developers will enhance the performance and scalability of applications using Supabase Auth.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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:
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.
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 Solution:
Additional Considerations:
Related issues:
Thank you for considering this request! Reducing the default cookie size and providing flexibility to developers will enhance the performance and scalability of applications using Supabase Auth.
Beta Was this translation helpful? Give feedback.
All reactions