I'm at the end of my rope on this one... i'm running into a cors issue in safari related to a content-type header. I own the backend and have confirmed it is returning "*" for Access-Control-Allow-Headers. Anyone have any ideas what this could be?
Asked
Active
Viewed 1,874 times
-1
-
Do you have the Safari response headers - they're not in that screenshot. – roryhewitt Jan 30 '18 at 21:37
-
i don't get any response headers in safari – vv1z Jan 31 '18 at 14:34
-
This worked for me: https://stackoverflow.com/questions/13146892/cors-access-control-allow-headers-wildcard-being-ignored – phazei Dec 13 '18 at 05:01
1 Answers
0
Turns out the issue was safari & ie don't honor * for this header so:
Access-Control-Allow-Headers: "*" is rejected.
After explicitly adding 'accept' and 'content-type' this was resolved:
Access-Control-Allow-Headers: "*, accept, content-type"
vv1z
- 467
- 4
- 8