You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross-origin Resource Sharing I won’t try to explain CORS, but in summary, browsers, by default, don’t allow JavaScript to make HTTP requests to domains other than the one the JavaScript was loaded from, and CORS is a way for servers to say that some domains are expected to make such “cross-origin” requests to them.
Rereading, I guess the "solution" we used isn't really less fiddly than the "return 200 on OPTIONS" one, and both depend on there even being a web server in front of WebSphere/Spring. Which won't be the case in a new architecture we're considering. So... another approach will have to be used at that time anyway.
CORS and WebSphere | Dougclectica Rebooted
Cross-origin Resource Sharing I won’t try to explain CORS, but in summary, browsers, by default, don’t allow JavaScript to make HTTP requests to domains other than the one the JavaScript was loaded from, and CORS is a way for servers to say that some domains are expected to make such “cross-origin” requests to them.
https://dougbreaux.github.io/2021/01/12/cors-and-websphere.html
The text was updated successfully, but these errors were encountered: