Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[HttpKernel] fix session tracking in surrogate master requests#27467
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
a15c14e to7b18ee6Compare7b18ee6 to146e01cComparenicolas-grekas commentedJun 6, 2018
(failure will be fixed once merged up to master) |
nicolas-grekas commentedJun 14, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
ping @symfony/deciders votes pending, this "just" fixes ESI with HttpCache, which are broken (found in training sessions by@jpauli ) |
stof left a comment
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.
Looks good to me
…ests (nicolas-grekas)This PR was merged into the 3.4 branch.Discussion----------[HttpKernel] fix session tracking in surrogate master requests| Q | A| ------------- | ---| Branch? | 3.4| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -Spotted while looking at ESI fragments resolved by`HttpCache`: right now when the master request starts the session, fragments are not cacheable anymore, even when they do not use the session.Commits-------146e01c [HttpKernel] fix session tracking in surrogate master requests
stefandoorn commentedJun 22, 2018
@nicolas-grekas Maybe unrelated, maybe not, I just upgraded from 3.4.2 to 3.4.11 on a site that heavily uses ESI fragments, and performance degraded within a second. Had to revert the upgrade (didn't expect this - locally no issue) to make performance be 'normal' again. Unfortunately no benchmarks or proper debug information available - locally also Blackfire doesnt show me any real differences. Might be related to this? |
nicolas-grekas commentedJun 22, 2018
Only a profile could tell... |
nicolas-grekas commentedJun 22, 2018
Maybe try branch 3.4-dev? |
stefandoorn commentedJun 22, 2018
Yeah, was afraid about that :-D Will see if I can get that :) And I'll try the dev branch, good one. |
stefandoorn commentedJun 22, 2018
I can confirm that on 3.4.2 files were being written to the |
danrot commentedJun 26, 2018
@nicolas-grekas Are you aware that the session is always used in tests now? That's because ofthis Isn't that something that should be fixed in Symfony? I don't really see a nice way of handling this in our codebase (there are a few ways, but I would consider all of them dirty). |
nicolas-grekas commentedJun 26, 2018
nicolas-grekas commentedJun 27, 2018
danrot commentedJun 29, 2018
Just tested it, it works 👍 Thanks a lot! |
Spotted while looking at ESI fragments resolved by
HttpCache: right now when the master request starts the session, fragments are not cacheable anymore, even when they do not use the session.