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
Request header field Content-Type is not allowed by Access-Control-Allow-Headers in preflight response. #22
Comments
Thanks for asking this question: I realized that I don't have any client-side examples. The configuration above will only work if the client sends a "simple" request, i.e.,
Hope that helps. |
@agrueneberg still getting the same error with your suggestion
|
What headers are sent in the request? I'm also surprised you're getting an |
Yes, it's Chrome Version 61.0.3163.91 (Official Build) (64-bit)
|
I see, in that case I would expect Akamai to handle CORS as well. There should be a way to configure those CORS-related headers? I'm wondering if the preflight requests ( |
This is the request request header |
I would suggest to temporarily take Akamai out of the equation, find out which CORS headers you need, and then figure out how Akamai is handling CORS. |
What am I missing? I follow the example but still getting pre-flight error
The text was updated successfully, but these errors were encountered: