Duplicate Form Key Cookie

[mvenghaus]

Preconditions and environment

• Magento 2.4.5

Steps to reproduce

1. Open any page with page cache enabled. Ex: https://demoshops.splendid-internet.de/magento/demoshop-magento2-daily/hero-hoodie.html -> first form_key by js

2. Select size & color -> second form_key by php

Expected result

one "form_key" cookie

Actual result

there are two cookies "form_key" "form_key"

Additional information

when the cookie is handled by php there is always a dot prefix in the domain

https://github.com/magento/magento2/blob/2.4-develop/lib/internal/Magento/Framework/View/Element/Js/Cookie.php#L64

when the js form-key-provider.js sets the cookie, there is no configuration for the domain and the cookie is set without the dot

https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/PageCache/view/frontend/web/js/form-key-provider.js#L30

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 @mvenghaus. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

  :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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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!

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

Hi @mvenghaus , Thank you for reporting and collaboration. Verified the issue on both Magento 2.4-develop instance and 2.4.5 project-community-edition as well but the issue is not reproducible. Only one "form_key" cookie is present as displayed below: Kindly check the behavior on Magento 2.4-develop instance / elaborate missing steps / configuration details if the issue is still reproducible. Thank you.

[mvenghaus]

@engcom-November

Step 1 open https://demoshops.splendid-internet.de/magento/demoshop-magento2-daily/hero-hoodie.html -> first form_key by js

Step 2 select size & color -> second form_key by php

.. and thx for the fast reply ;)

[engcom-November]

Thank you for the reponse @mvenghaus . Verified the issue again on Magento 2.4-develop instance with above mentioned steps and the issue is reproducible. Hence updating the description and confirming the issue.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-6833 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.

[github-jira-sync-bot]

:x: You don't have permission to export this issue.