Open william-gooch opened 5 months ago
Hi @william-gooch. 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@magento I am working on this
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.
@magento give me 2.4-develop instance
Hi @william-gooch. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Delta. 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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @william-gooch, here is your Magento Instance: https://e4f1dc96fd2a29c0dfef62b22c58308a.instances-prod.magento-community.engineering Admin access: https://e4f1dc96fd2a29c0dfef62b22c58308a.instances-prod.magento-community.engineering/admin_3d27 Login: 98152775 Password: bb2af77d0df9
Confirmed to occur on 2.4-develop instance
Hi @william-gooch ,
Verified the issue on 2.4.7 and 2.4-develop, it is reproducible.
Hence, Confirming the issue.
Steps to reproduce:-
2.4.7
2.4-develop
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-11997 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Just upgraded from 2.4.6-p6 to 2.4.7-p1. Bug appeared under 2.4.7.
When magento tries to recover the query it checks the request url or body based on HTTP METHOD in case of OPTIONS it returns an empty array that when parsed using graphql source triggers an error
overriding statusCode with 200 in case of OPTIONS method it works
Any updates/patch next release on the issue?
I get the following error in the exception.log
`Next Exception: Report ID: graph-ql-66acbdf8dc7a9; Message: Syntax Error: Unexpected
[previous exception] [object] (GraphQL\Error\SyntaxError(code: 0): Syntax Error: Unexpected
Preconditions and environment
Steps to reproduce
curl -i -X OPTIONS http://test.site/graphql
Expected result
Returns the "unexpected EOF" error but with a 200 status code so that CORS requests succeed.
Actual result
Returns the "unexpected EOF" error with a 500 status code, so CORS preflight requests always fail.
Additional information
This seems like it re-introduces MDVA-35312 which was previously fixed in Magento 2.4.3. I believe this is caused by https://github.com/magento/magento2/blame/c6bc8300e771e5e96ce9ac6c116746fe3de80544/app/code/Magento/GraphQl/Controller/GraphQl.php#L194 which parses the query and returns an error even if the request validators succeed.
Release note
No response
Triage and priority