I’ve got a Jets deployment with config.cors = true…as the documentation states, the deployed api on API Gateway is created to respond with various headers including Access-Control-AllowOrigin = ‘*’. Unfortunately my requests get rejected at the browser still.
I’m no CORS expert, far from it, but all documentation I can find says the header name should be Access-Control-Allow-Origin.
When I brute force that header name into the api response, everything works as expected.
Dove tailing off my comment about not being a CORS expert…is the missing hyphen in the header name Jets sets up a bug or am I doing something incorrectly?
Any assistance would be greatly appreciated.