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

Save Paella preferences in Local Storage instead of a cookie? #322

Closed
karendolan opened this issue Sep 8, 2023 · 0 comments
Closed

Save Paella preferences in Local Storage instead of a cookie? #322

karendolan opened this issue Sep 8, 2023 · 0 comments

Comments

@karendolan
Copy link
Contributor

Some of our students are getting "HTTP 431 header too large" errors on player requests. This is probably because of other large cookies in their browser. While we were debugging, we notice that the Paella 7 preference cookie is quit large, and will get larger as our students visit more videos through Paella 7. Our site uses session cookies, so all the cookies get sent on each request from Paella 7.

Other sites, like https://github.com, save preferences to the browser Local Storage. Is it possible for Paella 7 to save it's preferences data to the browser local storage area instead of to a cookie? This would cut down on the request header size for our students.

@karendolan karendolan changed the title Paella preferences are in browser cookie instead of Local Storage? Save Paella preferences in Local Storage instead of a cookie? Sep 8, 2023
mliradelc pushed a commit to opencast/opencast that referenced this issue Oct 9, 2023
…ades Paella core to 1.43 (#5253)

This PR updates the paella to last version and updates the config file
to save the user preferences in the localstorage instead of cookies.
Fixes a "HTTP 431 header too large" bug when user's preferences are too
large.
See polimediaupv/paella-core#322

### Your pull request should…

* [x] have a concise title
* [ ] [close an accompanying
issue](https://help.github.com/en/articles/closing-issues-using-keywords)
if one exists
* [ ] [be against the correct
branch](https://docs.opencast.org/develop/developer/development-process#acceptance-criteria-for-patches-in-different-versions)
* [ ] include migration scripts and documentation, if appropriate
* [x] pass automated tests
* [x] have a clean commit history
* [x] [have proper commit messages (title and body) for all
commits](https://medium.com/@steveamaza/e028865e5791)
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

No branches or pull requests

1 participant