Skip to content
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

2021/01/12/cors-and-websphere #29

Open
utterances-bot opened this issue Jan 19, 2022 · 2 comments
Open

2021/01/12/cors-and-websphere #29

utterances-bot opened this issue Jan 19, 2022 · 2 comments

Comments

@utterances-bot
Copy link

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

Copy link
Owner

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.

Copy link
Owner

See follow-up for Liberty and Kubernetes at https://dougbreaux.github.io/2023/10/03/cors-with-liberty.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants