Long cookies #7742
Long cookies
#7742
Replies: 2 comments 14 replies
-
That specific length - 4096 bytes - is not an accident. It's actually a limitation of browsers themselves, not the Remix API. http://browsercookielimits.iain.guru You've got a couple of options here:
|
Beta Was this translation helpful? Give feedback.
9 replies
-
@KnisterPeter, what did you end up doing? I'm looking at the exact same situation. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
the current
SessionStorage
api does not allow cookies which are too long. The default implementation throws if a cookie is more than 4096 bytes. This could be too short if there are longer data to be stored which would required multiple cookies to encode/decode all data.I understand that this is not part of the default cookie implementation, but the current API of the session storage does only return a single string (cookie header) from the
commitSession
call. It does not even receive a response object to write additional headers (multiple cookies) or deal with that in any other way.Someone elso also has this issue already? How to deal with that?
(e.g. we would like to use
remix-auth
with OAuth2 strategy. And the resulting token, refresh-token, id-token are too long for a cookie)Beta Was this translation helpful? Give feedback.
All reactions