Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

frontend: base64 encode cookies #198

Merged
merged 1 commit into from
Aug 29, 2022
Merged

frontend: base64 encode cookies #198

merged 1 commit into from
Aug 29, 2022

Conversation

ali-abrar
Copy link
Member

To maximize compatibility with user agents, servers that wish to
store arbitrary data in a cookie-value SHOULD encode that data, for
example, using Base64

https://www.rfc-editor.org/rfc/rfc6265

To maximize compatibility with user agents, servers that wish to
   store arbitrary data in a cookie-value SHOULD encode that data, for
   example, using Base64

https://www.rfc-editor.org/rfc/rfc6265
server-side as well, so that widgets that depend on the cookie can be
prerendered. The functions in this module use javascript and, so, cannot be
rendered server-side. If you're mixing the two, bear in mind that obelisk does
not currently demand that cookies be base64-encoded, while this module does,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gonna make an obelisk issue for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants