Do not set cookie if not required #70
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As currently implemented, flask session will add the set-cookie header to every request including static files, etc. this prevents most standard caching setups. We should call
self.should_set_cookie()to determine if the set-cookie header should be included.With flask default config, this doesn't actually modify the set-cookie header behavior. But, with this change, and by setting
SESSION_REFRESH_EACH_REQUESTto False in the flask app config, the set-cookie header will only be included whensession.modifiedis True. This attribute is set anytime one modifies the session, but can also be set manually in specific flask views if needed to update session timeouts.