-
Notifications
You must be signed in to change notification settings - Fork 111
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
support for chunked cookies #35
Comments
@zandbelt, Thanks. I saw that report. We should consider adding this support to |
I don't think there's a real standard; it doesn't really need one because its all "internal"; the process would be:
On retrieval one would check whether a cookie named For an idea of the effort, see: There's still a limitation in the maximum size of the (single) "Cookie" header that the browser will actually manage to send, but that is known to be much larger (typically at least 81920), see: |
Okay. I can think about implementing this. Thank you. I already started looking at it. |
The first try to do this is implemented in these commits: BEWARE! I just wrote the code, but I have not run it. That means that there could be some nasty bugs. Also in this version the I don't have time to test this thoroughly right now. But all the feedback is welcomed. |
I made some obvious fixes after the comment above. |
Okay, it got some nasty bugs, but those are resolved now. Can you please try it out and report back to me if it works as expected. Note: please also adjust your Nginx config as needed, e.g. to accept larger cookies, you may need to add something like this in large_client_header_buffers 4 16k; |
This is now released as a part of 2.15 release. |
Using the default cookie storage it may happen that the size of the cookie runs over browser limits when a lot of data is stored in the session. Adding support for chunked cookies would mitigate this somewhat. See: zmartzone/lua-resty-openidc#33
The text was updated successfully, but these errors were encountered: