[MGNLADVCACHE-118] Personalized variant will displayed for not personalized user Created: 22/Feb/17 Updated: 02/Mar/23 |
|
| Status: | Accepted |
| Project: | Advanced Cache |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Frank Sommer | Assignee: | Robert Šiška |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | maintenance, to-estimate, to-verify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Component personalization |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Support | ||||||||
| Team: | |||||||||
| Description |
|
On demo instance (M5.5.2) I can reproduce this issue. Follow these steps:
Another way to reproduce (from ahietala):
|
| Comments |
| Comment by Rainer Blumenthal [ 28/Feb/17 ] |
|
Are there any news on this? Tomorrow I have to pressent the solution to the customer - and I'd like to give them a timeline for the fix. |
| Comment by Antti Hietala [ 28/Feb/17 ] |
|
rainer, the issue is currently being worked on (In Progress). The fix will be in the next maintenance release, Magnolia 5.5.3. Release date is not set yet, expected in March. |
| Comment by Robert Šiška [ 02/Mar/17 ] |
|
Hello. We couldn't reproduce this issue with given steps on 5.5.3 nor 5.4.12 (with cp13n) and neither on current demo (5.5.2). Best regards, |
| Comment by Frank Sommer [ 03/Mar/17 ] |
|
I can still reproduce it. It doesn't depends on the browser cache. |
| Comment by Rainer Blumenthal [ 03/Mar/17 ] |
|
Video of the bug: https://www.dropbox.com/s/ie5mfbxfsbd2zv6/2017-03-03_1205.swf?dl=0 It is easy to reproduce ... |
| Comment by Roman Kovařík [ 13/Mar/17 ] |
|
Hello rainer, This is how the caching of personalized pages should work (and works when we test it from our side):
It looks like you are somehow able to create an invalid cache entry. Thanks in advance. |
| Comment by Frank Sommer [ 14/Mar/17 ] |
|
Hello Roman, hello Jan, Requirements
Error case
Working case |
| Comment by Roman Kovařík [ 17/Mar/17 ] |
|
Hi frank.sommer For the error case, could you check that the created cache entry is incorrect? (use the download action, it's shouldn't be possible to download the personalized cache entry, if it's possible to download it, the cache entry is wrong). Best regards |
| Comment by Frank Sommer [ 20/Mar/17 ] |
|
Hi Roman, I attached screenshots from the requests for reproducing the error case. When I request the page from other network and other device, it is still the same errornous response. Until 9:30 you would see the same response in your browser for https://demopublic.magnolia-cms.com/. After that just call me and I will easily (just in two requests) set the demo instance in that state. |
| Comment by Roman Kovařík [ 23/Mar/17 ] |
|
Hi frank.sommer,
|
| Comment by Frank Sommer [ 04/Apr/17 ] |
|
I can still reproduce this issue and had the cache classes set to debug. But in error case only one message is logged in the magnolia-debug.log file. DEBUG info.magnolia.advancedcache.personalization.cache.PersonalizedCacheStore 04.04.2017 10:06:51 -- Default: info.magnolia.module.cache.filter.InMemoryCachedEntry@6c199a1d[gzippedContent=5768 bytes,plainContent=28808 bytes,contentType=text/html;charset=UTF-8,characterEncoding=UTF-8,statusCode=200,serializableHeadersBackingList=<null>,lastModificationTime=1491293210758,originalUrl=https://demopublic.magnolia-cms.com/,timeToLiveInSeconds=-1] On request with the second browser (no-cookie) no further log messages will be logged. |
| Comment by Roman Kovařík [ 05/Apr/17 ] |
|
Hi frank.sommer, |
| Comment by Robert Šiška [ 13/Apr/17 ] |
|
Hello frank.sommer Could you please reproduce the issue once again, download the DEBUG log and send it to us? Thank you, |
| Comment by Rainer Blumenthal [ 13/Apr/17 ] |
|
frank is back on tuesday |
| Comment by Antti Hietala [ 28/Apr/17 ] |
|
rainer / frank.sommer Do you have an update on this? Kindly try to reproduce. |
| Comment by Frank Sommer [ 12/May/17 ] |
|
It's still easy to reproduce for us. In error case only one line is still logged. DEBUG info.magnolia.advancedcache.personalization.cache.PersonalizedCacheStore 12.05.2017 14:46:24 -- Default: info.magnolia.module.cache.filter.InMemoryCachedEntry@7036bd05[gzippedContent=5768 bytes,plainContent=28808 bytes,contentType=text/html;charset=UTF-8,characterEncoding=UTF-8,statusCode=200,serializableHeadersBackingList=<null>,lastModificationTime=1494593183891,originalUrl=https://demopublic.magnolia-cms.com/,timeToLiveInSeconds=-1] In success case there are some more lines in the log file. The whole log file is attached. See magnolia-debug.log It is reproducable by https://demo-features.magnolia-cms.com/travel/, too. |
| Comment by Rainer Blumenthal [ 15/May/17 ] |
|
Now the feature is about to be used in the LIVE system and I assume we will come back to you soon with very high pressure. This or the latest next week, it will cause a lot of trouble. We posted 3 different ways to reproduce with really excellent screenshots and explanations, had two teamviewer sessions, and 2 times did the "log-file thing" meanwhile I really feel a little lost. On our side everybody can reproduce it, and the behaviour did not change since february. On Magnolia side nobody ever made it. Did you ever try with a windows environment (Firefox / Chrome)? |
| Comment by Rainer Blumenthal [ 15/May/17 ] |
|
We found out sth. interesting If we first "clear the cache" and then do
So there is sth. strange happening if the first request (after Cache flush) comes from within the Aperto network.
|
| Comment by Karel de Witte [ 23/May/17 ] |
|
Hi Rainer, Could you try to exclude magnolia's domain from your intranet proxy's cache ? Best regards, |
| Comment by Frank Sommer [ 23/May/17 ] |
|
Sorry, I don't understand the relationship between a proxy cache and the wrong p13n cache state in Magnolia CMS. I mentioned before, that we could easily set the Magnolia CMS in this wrong state and after that everybody (Magnolia employees itself) see the wrong state in their browsers. |