FPC not work when login

[rogerdz]

Preconditions and environment

• Magento version 2.4-develop

Steps to reproduce

1. Set develop mode: bin/magento deploy:mode:set developer
2. Login customer
3. Clear cache: bin/magento cache:clean
4. Load homepage
5. Reload homepage and check x-magento-cache-debug header

Expected result

need response with x-magento-cache-debug: HIT

Actual result

response with x-magento-cache-debug: MISS => page not load from cache in fpc

Additional information

No response

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[bot]]

Hi @rogerdz. 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.

• 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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[bot]]

Hi @engcom-November. 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: :point_down:

• [ ] 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

  - 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!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @rogerdz ,

Thank You for your report and collabration.

We have reviewed the reported issue and attempted to reproduce it in the both latest 2.4-develop instances. However, we were unable to replicate the issue on our end. Please find the attached screenshot for the reference.

Step to Reproduce

• Set develop mode: bin/magento deploy:mode:set developer
• Login customer
• Clear cache: bin/magento cache:clean
• Load homepage
• Reload homepage and check x-magento-cache-debug header

As we followed the precondition and steps we didn't encounter any issue, Kindly reverify the issue once from your side and let us know if we may have missing anything.

Hence we marking this issue as "Needs Update"

Thank You again!

[rogerdz]

Hi @engcom-November

Are you using build in fpc or varnish? Please test with build-in fpc

[engcom-November]

Hello @rogerdz ,

Thank you for the report and collaboration.

We have attempted to reproduce the issue and can confirm it is reproducible on our latest 2.4-develop branch. Please see the attached screenshot for reference.

Steps to Reproduce:

• Set developer mode: bin/magento deploy:mode:set developer
• Login as a customer
• Clear cache: bin/magento cache:clean
• Load the homepage
• Reload the homepage and check the x-magento-cache-debug header

Following these preconditions and steps, we have encountered the issue.

Therefore, we are marking this issue as Confirmed.

Thank you again for your collaboration!

[github-jira-sync-bot]

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

[m2-assistant[bot]]

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

[engcom-Bravo]

Hi @rogerdz,

Adobe Commerce Engineering team started working on this issue. We will reach out to you if we need more information and you will get notified once the issue is fixed. Please leave comments for any further questions.

Thank you!

[engcom-Bravo]

Hi @rogerdz,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-14999 by the internal team Related commits:https://github.com/search?q=repo%3Amagento%2Fmagento2+AC-14999&type=commits

Based on the Jira ticket, the target version is 2.4.9-alpha2.

Thanks

[rhoerr]

For anyone else that ends up here, the specific fix is in commit https://github.com/magento/magento2/commit/12d490ba60164b44a8c35e4a0b31f4997fb759ae

This is the same as proposed in https://github.com/magento/magento2/pull/40008 (plus a test). See also https://github.com/magento/magento2/issues/40039.