Skip to content
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

Using Varnish Cache with PWA Stuido #86

Open
secaliskan opened this issue Jun 13, 2024 · 1 comment
Open

Using Varnish Cache with PWA Stuido #86

secaliskan opened this issue Jun 13, 2024 · 1 comment
Assignees

Comments

@secaliskan
Copy link

💡 Feature request

Feature Name

PWA Stuido GraphQL POST request Fix for Varnish cache

The Desired Behavior

When we activate Varnish cache at Magento backend also update the default.vcl at varnish server; PWA stuid frontend working fine;
GET queries are cacheable - should be working
POSt request are not cacheable -should be working

Your Use Case

Varnish enabled n different server with IP; backlend is in the same env with internal ip does not have a public IP
Varnish configuration on Magento Admin has been set correctly.
Exported varnish VCL updated in Varnsh server.
Website is working and Varnish caching is working
When we see the network GraphQL GET queries working fine. we can render catalog and product pages.

But whem we come to graphql POST request its giving 500 Internal server error.
IMO Get query content-type are application/json
But POST actions content-type is text/html

So its giving Internal Server error 500

Prior Work

Environment


magento2-cors version:  I dont know
Magento version: 2.4.5 p1
PHP Version version: 8.1
Varnish cache: Verison 6.012

Varnish cache is at another Server with Public IP ; Magento app server is in different server. with internal IP..




Others:

@damienwebdev
Copy link
Member

Why do you think this is an error with the CORS plugin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants