Skip to content

Conversation

@nitriques
Copy link
Member

This commit simply checks, for each event attached to the page, if there
is a filter with xsrf in its name. If so, it will make sure that the
token is generated.

Hopefully, this fixes #2173 for good.

This commit simply checks, for each event attached to the page, if there
is a filter with `xsrf` in its name. If so, it will make sure that the
token is generated.

Hopefully, this fixes symphonycms#2173 for good.
Copy link
Member

@michael-e michael-e left a comment

Choose a reason for hiding this comment

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

I did some tests, and this seems to work fine. It will potentially reduce the number of generated sessions. However, we should be aware that those sessions — once generated — will stay. There is no mechanism to remove old/superfluous XSRF tokens from sessions, so the sessions won't be cleaned up. (Symphony is not very good in cleaning up sessions anyway.)

IMHO it would add a lot of complexity to properly clean up tokens and sessions, and anyway the main issue is fixed here. So "thumbs up"!

Copy link
Member

@brendo brendo left a comment

Choose a reason for hiding this comment

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

LGTM!

@nitriques nitriques modified the milestones: 2.7.11, 3.0.0 Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants