New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
admin | Some cookies are misusing the recommended “SameSite“ attribute #34461
Comments
Hi @salehawal. Thank you for your report.
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:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 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. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@salehawal, |
@salehawal, just checker further - it looks like these cookies are set automatically on the top domain on the Magento Cloud and it's not related to the Magento Open Source (or EE / B2B). I think you should contact your Magento Cloud support for that. |
@ihor-sviziev .. this is from ssl localhost, the domain is set via /etc/hosts and the app server is apapche2 |
@salehawal, so in this case you should remove the AMCV_* and AMCVS_* cookies manually. |
@ihor-sviziev .. i searched the entire code base for "AMCV_" i cant find the file? |
@salehawal these cookies are saved in your browser. Magento doesn't set them. |
@ihor-sviziev is included here: so now is there why to fix this or i should just comment it out? |
@salehawal, I think it shouldn't cause any issues to the non-analytics functionality of the admin page. |
for now this is the solution: 2- rebuild magento and clear the cache
3- clear browser cache and reload the admin page |
it is also related to this issue : #34476 |
i have resolved the issue by downloading the file "https://assets.adobedtm.com/a7d65461e54e/37baabec1b6e/launch-177bc126c8e6.js" and move it under /pub directory ad updating caller url with the new url of edited file as follow:
2- update the file call url in "/app/code/Magento/AdminAnalytics/view/adminhtml/layout/default.xml"
it is a quick and dirty solution, but i hope for a better solution in the next update but it seems that admin is still not resolved and the problem for it spinning forever was not the same site issue from the start so we move on with the spinner issue on this ticket #34476 |
Hi @engcom-Hotel. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Hotel, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
@magento give me 2.4-develop instance |
Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Hotel, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-November, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
1 similar comment
Hi @engcom-November, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-November, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
@magento give me 2.4-develop instance |
Hi @slavvka. Thank you for your request. I'm working on Magento instance for you. |
Hi @slavvka, here is your Magento Instance: https://bb008153671d2b1378ba423268d9815a.instances.magento-community.engineering |
@magento give me 2.4-develop instance |
Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Hotel, here is your Magento Instance: https://bb008153671d2b1378ba423268d9815a.instances.magento-community.engineering |
Hi @salehawal, Thank you for reporting the issue. I have tried this issue on the fresh installation Magento 2.4-dev but I am not able to reproduce it. Kindly recheck the issue on Magento 2.4-develop branch and elaborate the steps if the issue is still reproducible. |
Dear @salehawal, We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this. Regards |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
2.
The text was updated successfully, but these errors were encountered: