2 ms·
But were the headers reaching the browser or not? CORS is something strictly for the browsers to parse, so if it's reaching the browser, either the policy is wr
by icebraining 7y ago
But were the headers reaching the browser or not? CORS is something strictly for the browsers to parse, so if it's reaching the browser, either the policy is wrong (and you can usually see that in the browser console, when it blocks the cross-domain request) or it's not a CORS problem.
- jedberg 7y agoIt wasn’t reaching the browser.
- icebraining 7y agoSeems like you have to whitelist the headers: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/header-caching.html#header-caching-web-cors https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...
- jedberg 7y agoI did, but it still didn't work. It was extra complicated because it was coming out of API gateway calling Lambda. But the point is, it shouldn't be that complex and I shouldn't have to dive deep into the docs to make it work. That is as much an impediment to CORS as is the lack of understanding.