-
Notifications
You must be signed in to change notification settings - Fork 32
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 withForm #48
Comments
We were testing out this plugin as a replacement for container based sessions, but ran into the same withForm issue. The form token appears to be added to the session after render is called as it's generated in the gsp. Because the gsp is rendered after grails has set the status on the request, there is no chance to capture further changes to the session, and write out the new cookies. I have a fix for this that I'll do a pull request for shortly. |
great. that will be much appreciated. looking forward to it. |
hey exell-christopher, were you able to test your changes with the test-suite as described in the response to your pull request? -ben |
I haven't had a chance to get back to this yet. Hoping to sometime this On Mon, Apr 13, 2015 at 10:32 AM, Ben Lucchesi [email protected]
|
Fixed in https://github.com/double16/grails-cookie-session/tree/release/4.0.0 dependencies { |
It looks like the object used to hold keys used by the withForm method isn't serializable and is getting dropped from the session object. either that or the object isn't getting written to/read from the session before or after the cookie session is loaded. need to investigate.
The text was updated successfully, but these errors were encountered: