-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fix unexpected "Vary" #735
Open
jrobichaud
wants to merge
4
commits into
main
Choose a base branch
from
unexpected-vary
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this is working as expected, I'm not sure this is the best way to go, because we're accessing user and then lying to SessionMiddleware basically.
I see two possible alternatives here.
1. Use truly lazy user_id, something along these lines:
If log level is higher than info, these variables (
logger.info("request_started", **log_kwargs)
) aren't used, so we do not accessuser_id
at all. NoVary: Cookie
.But, with log level <= INFO, those logs are written, and so
Vary: Cookie
added.2. Check if request.session was already accessed, and add user_id only in this case.
That's also lying but from another angle - request was authorized, but it does not matter because user was not accessed.
I would prefer first option, because it's truly lazy and reflects reality as close as possible.
But, if you think modifying
request.session.accessed
is safe approach - it's good enough for me. Request has no vary: Cookie and that is what matters most.After we agree on the best approach here, let me check this one more time in real app scenario, and I'll report back how it works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The purpose of Vary is to tell if the content returned may change for caching purpose.
Normally checking if the user has been accessed is a good way to tell if the content may change. Ex: a condition to render something based on the user, checking permissions, etc.
However django-structlog accessing the user won't affect the template at all.
django-structlog
needs to tell which user accessed a route even if the user was not accessed in the view.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair point. I have tested this code and it works as expected.
I had to make some minor changes, to catch a case when this was included before AuthenticationMiddleware, and my final version looks like this: