[Area: Frontend] Unrelated cache tags added to X-Magento-Tags header on CMS pages

[ananth-iyer]

Preconditions and environment

• Magento version - 2.4.6-p1
• PHP - 8.1
• Built-in FPC Cache

Steps to reproduce

1. Open Homepage and note down value of X-Magento-Tags in response header.
2. Open any CMS page like About US, Privacy Policy or new page
3. You will notice the same values in X-Magento-Tags whether there are no products, categories, or static blocks. It will show same value on any CMS pages.
4. For example:
   cat_c,cat_c_38,cat_c_20,cat_c_11,cat_c_3,cat_c_9,cat_c_37,store,cms_b,cms_b_1,cms_b_footer_links_block,cms_b_14,cms_b_home-page-block,cms_p_2,cat_p,FPC

Expected result

As per my understanding, there should be no cat_c and cat_p in X-Magento-Tags header when there are no products & categories on that page.
When visiting any CMS page that it should not contain cat_c and cat_p when it is does not have category and products. It should add page id, static block id related tags only.
It affacts the website overall performance and Google ranking.

Actual result

When visiting any CMS page that it contains cat_c and cat_p in X-Magento-Tags header when CMS page does not have category and products.

Additional information

Additionally, it also causes full FPC cleanup when the product or category is saved and its ID is added in the X-Magento-Tags header and present in CMS pages.
I assume the navigation menu is conflicting with the cache tags.
For reference:
cat_c_{category_id} - cat_c_1
cat_p_{product_id} - cat_p_1
cms_b_{static_block_id} - cms_b_1

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ananth-iyer. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Dash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Dash, here is your Magento Instance: https://cbfe4aa081b6004cb6bc5340ceeb5349.instances-prod.magento-community.engineering
Admin access: https://cbfe4aa081b6004cb6bc5340ceeb5349.instances-prod.magento-community.engineering/admin_4714
Login: 5c6b4ad0
Password: 1c738fd17506

[ananth-iyer]

@engcom-Dash X-Magento-Tags and X-Magento-Cache-Debug headers still not showing even in developer mode. I assume the web server is removing the headers.

[chandresh-rana]

Hello,

I got the same issue on Magento 2.4.6-p1. When I update any product from admin panel or through rest API the whole Magento cache is being refresh.

For testing, Simply create a custom CMS page and update any product like stock or sku then check that created CMS page will be added to X-Magento-Cache-Debug: MISS. Even I don't touch that cms page or not added that page link to anywhere in Magento.

[engcom-Dash]

Hi @ananth-iyer

Verified the issue in 2.4-develop instance and the issue is reproducible, Hence we are confirming the issue.
Kindly refer the below screenshots:

When we visiting CMS page that it contains cat_c and cat_p in X-Magento-Tags header as per the actual result.

Thanks.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-9258 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[ananth-iyer]

@engcom-Dash Thank you for taking time and confirming the issue. When can we expect the issue to get resolved? Kindly let us know if there is any quick workaround patch.

[engcom-Bravo]

Hi @ananth-iyer,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is still reproducible.Kindly refer the screenshots.

When visiting any CMS page that it contains cat_c and cat_p in X-Magento-Tags header when CMS page does not have category and products.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-9258

[ananth-iyer]

Hi @engcom-Bravo After so many months the issue is reproducible in latest version. Let's hope the issue will get fixed sooner.