# Developing the "OCL for OpenMRS" Application

**URL:** <https://talk.openmrs.org/t/developing-the-ocl-for-openmrs-application/17771>\
**Category:** Development\
**Created:** [April 26, 2018, 9:03pm UTC](https://talk.openmrs.org/t/developing-the-ocl-for-openmrs-application/17771 "2018-04-26T21:03:33Z")\
**Posts on this page:** 1\
**Showing post:** 376

<div class="post-metadata">

**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\
**Post date:** [November 27, 2018, 10:25am UTC](https://talk.openmrs.org/t/developing-the-ocl-for-openmrs-application/17771/376 "2018-11-27T10:25:21Z")

</div>

> [@abulojoshua1](#):
>
> you can reach out to him and you guys work on the CORS issue

Searching by ‘CORS’ in talk, one of the first hits is [this one](https://talk.openmrs.org/t/cross-origin-resource-sharing-cors-affecting-the-development-of-ocl/19124/1).

This is the answer of how I implemented it:

> [@Cross-Origin Resource Sharing (CORS) affecting the development of OCL](https://talk.openmrs.org/t/cross-origin-resource-sharing-cors-affecting-the-development-of-ocl/19124/41):
>
> Got it. It’s important to follow up on this kind of thing, so we can actually action on it. None of us really understand CORS in detail, and we do not understand your app, so we need some feedback so we can actually do something about it. This is what ended up working: location / { if ($request\_method = 'OPTIONS') { add\_header 'Access-Control-Allow-Origin' '\*'; add\_header 'Access-Control-Allow-Methods' 'GET, OPTIONS, POST'; add\_header 'Access-Control-Allo…

I made it available for PUT, GET and POST, as requested.

I can add to DELETE too, while I’m not sure if the backend is prepared to receive it.

---

_[View the full topic](https://talk.openmrs.org/t/developing-the-ocl-for-openmrs-application/17771)._