AEMaacs Graphql Preflight Test | Community
Skip to main content
Sean-McK
New Participant
December 12, 2022
Solved

AEMaacs Graphql Preflight Test

  • December 12, 2022
  • 1 reply
  • 616 views

Hey All,

 

So working through all these CORS issues. I was able to fix all the issues on my local box but when I get to dev (cloud), I am getting a 204 on my preflight. Then after that, I get a 404

 

1) (preflight call) endpoint.json?operationName=getFooter&variables=%7B%7D&query=query%20getFooter%20%7B%0A%20%20footerList%20%7B%0A%20%20%20%20items%20%7B%0A%20%20%20%20%20%20footerCompanyName%0A%20%20%20%20%2 ..... This gets a 204 response

2) endpoint.json?operationName=getFooter&variables=%7B%7D&query=query%20getFooter%20%7B%0A%20%20footerList%20%7B%0A%20%20%20%20items%20%7B%0A%20%20%20%20%20%20footerCompanyName%0A%20%20%20%20%2 ..... 404

 

Any suggesstions. We are trying to use AEM totally headless with Graphql

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ritesh_Mittal

Hi @sean-mck ,

 

Assuming because preflight called got 204 response the second call failed and got 404. Could you please see below thread once. Just to check the CORS issue which you fixed on local I assume you have all set on Dev ie, 'Apache Sling Referrer Filter, Adobe Granite CSRF Filter'.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-postback-gives-http-204-instead-of-http-200/td-p/384108

1 reply

Ritesh_Mittal
Ritesh_MittalAccepted solution
New Participant
January 26, 2023

Hi @sean-mck ,

 

Assuming because preflight called got 204 response the second call failed and got 404. Could you please see below thread once. Just to check the CORS issue which you fixed on local I assume you have all set on Dev ie, 'Apache Sling Referrer Filter, Adobe Granite CSRF Filter'.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-postback-gives-http-204-instead-of-http-200/td-p/384108