Open suyuee opened 1 year ago
If someone can confirm this is indeed an issue, I can try to put up a fix
This is also broken for us when using the directResponseAction
config. I'm guessing that it bypasses settings the CORS headers in that scenario.
Actually for us it might be the method Matcher config as outlined in the issue here: https://github.com/solo-io/gloo/issues/3774
Unfortunately CORS support just seems really broken in gloo and no config so far works (as outlined in the issue above, 404 responses don't send cors headers back).
Gloo Edge Product
Open Source
Gloo Edge Version
v 1.15.1
Kubernetes Version
v 1.27.3
Describe the bug
The CORS policy in virtual host options do not add CORS headers like "Access-Control-Allow-Methods" to response. Would appreciate any help
Sample response (notice no cors headers)
Expected Behavior
When setting cors policy in virtual service, in request response (OPTIONS or other), there should be headers like allowed methods/origins/headers attached, but there aren't.
Steps to reproduce the bug
curl -i $(glooctl proxy url)/d0
Additional Environment Detail
I have tried both on eks and minikube
Additional Context
No response