[MGNLCACHE-198] Cache stores an 'empty' record when partial request + forward is done Created: 03/Apr/18  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Cache Modules
Component/s: cache core
Affects Version/s: 5.4.3, 5.5.7
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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:

 Description   

There is a situation when in cache it is stored an 'empty' page. If you do a partial request to an URL that is forwarded because a virtualUri and cache has to store the request, then an empty page is stored in cache and next time that the URL is requested a blank page is displayed.

Steps to reproduce the issue:

  1. go to http://localhost:8080/magnoliaPublic/.magnolia/admincentral#app:configuration:;/modules/ui-admincentral/virtualURIMapping/default and change "redirect" to "forward"
  2. If you are working with travel demo, you need to remove personalization in root page in order not to bypass cache
  3. flush cache
  4. curl http://localhost:8080/magnoliaPublic/ -i -H "Range: bytes=0-20" > Expected 206 response
  5. curl http://localhost:8080/magnoliaPublic/ -i > Unexpected 206 response (content is gotten from cache)
  6. In the browser go to http://localhost:8080/magnoliaPublic/ and a white page will be displayed (content is gotten from cache).

I am not able to reproduce it in Magnolia 5.6, two registers are created in cache for this version.



 Comments   
Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

Generated at Sun Feb 11 23:53:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.