# Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin'

**URL:** https://discuss.elastic.co/t/response-to-preflight-request-doesnt-pass-access-control-check-no-access-control-allow-origin/82571
**Category:** Kibana
**Created:** [April 17, 2017, 11:35am UTC](https://discuss.elastic.co/t/response-to-preflight-request-doesnt-pass-access-control-check-no-access-control-allow-origin/82571 "2017-04-17T11:35:43Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![jhn134910](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@jhn134910](https://discuss.elastic.co/u/jhn134910)
#### Post date: [April 20, 2017, 7:14am UTC](https://discuss.elastic.co/t/response-to-preflight-request-doesnt-pass-access-control-check-no-access-control-allow-origin/82571/7 "2017-04-20T07:14:33Z")

</div>

Looks like even though elastic-search supports CORS, kibana does not and there doesn't appear to be any handling for Options requests.

The only solution I came up with for my requirements was to introduce a web-proxy in front of kibana, so that kibana and my other services were running in the same domain. For that I used nginx and the steps documented at

> [@Can someone share nginx config for reverse proxying Kibana4.4/4,5](https://discuss.elastic.co/t/can-someone-share-nginx-config-for-reverse-proxying-kibana4-4-4-5/46326/8):
>
> here:

---

_[View the full topic](https://discuss.elastic.co/t/response-to-preflight-request-doesnt-pass-access-control-check-no-access-control-allow-origin/82571)._