-
Notifications
You must be signed in to change notification settings - Fork 75
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
openhim-core cors #981
Comments
Hi bwighane. Thank you for logging this issue. Our team will log a ticket to investigate whether this is a bug within the core, or a possible implementation issue. |
Hi Martin, I was able to go through The OpenHIM core implementation and make efforts to enable CORS when making AJAX requests. If perhaps there is a way of enabling that without messing with The OpenHIM code please advice. Thanks. |
Hi bwighane, Im unfortunately not aware of a way to do that without changing the code. This seems to be a bug, and will need proper fixing. We will investigate this issue and deploy a fix once resolved |
Hi, was this issue solved? I am facing the same in 2025. |
Hi @pierrekasongo, |
Hi @drizzentic, I want to consume my mediator API from a frontend on different IP address. The requests are blocked due to cors. |
@pierrekasongo Okay that will work. Another secure way would be to deploy everything behind a reverse proxy like Nginx. While in a development environment, you can use Chrome without security. Otherwise, the other available options include modifying the code. We don't currently have this configurable, but I will run it by the team to see if we can add a flag to disable cors or allow certain origins. |
I can only access a public channel when making Ajax requests but cannot do the same to a private channel. Is the OpenHIM core cors enabled by default?
The text was updated successfully, but these errors were encountered: