I'm getting Cross-Origin Request Blocked error since 2 weeks
See original GitHub issueHi;
I was successfully using the library. But since 2 weeks, I started to get CORS error. What is the proper way to fix that?
UPDATE: In Chrome, I am getting following:
Request header field Authorization is not allowed by Access-Control-Allow-Headers
Issue Analytics
- State:
- Created 8 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
What Is a CORS Error and How to Fix It (3 Ways) - Bannerbear
A CORS error is common when making an HTTP request to another origin. You can get rid of it using one of the...
Read more >CORS errors and how to solve them - Topcoder
CORS is an abbreviation for Cross-Origin Response Sharing. It is what allows the website on one URL to request data from a different...
Read more >I got a CORS error, now what? - DEV Community
The reason is when a CORS error appears, your browser immediately discards the error data to prevent it from being used maliciously.
Read more >How to fix a CORS (cross origin request) error for local host in ...
If you are getting a CORS ( cross origin request ) error when trying to display a localhost webpage there may be an...
Read more >Fix CORS Error Permanently Regardless of Your Web App
By the end of this section, you'll know how to get rid of the ugly CORS error permanently no matter what type of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@burakkilic I found that other libraries are adding the Authorization header to the request. One such library is Satellizer.js.
@spacepang’s suggestion (skipAuthorization) works for satellizer too.
If you are still experiencing this issue, verify that other scripts are not modifying the request. (In Angular this is normally done using $httpProvider.interceptors.)
I’m closing this ticket as it is not a cloudinary_angular issue. However please feel free to open an issue here or at http://support.cloudinary.com/hc/en-us if you still have a problem.
I’d appreciate it if you drop a note here if you manage to solve the issue too!
But I do not send the Authorization header. Also it is not seen in the screenshots above.
I also added
to my request but nothing has changed.