# ElasticSearch allows only GET requests

**URL:** <https://discuss.elastic.co/t/elasticsearch-allows-only-get-requests/46059>\
**Category:** Elasticsearch\
**Created:** [April 1, 2016, 12:40pm UTC](https://discuss.elastic.co/t/elasticsearch-allows-only-get-requests/46059 "2016-04-01T12:40:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![edeak](https://avatars.discourse-cdn.com/v4/letter/e/a698b9/32.png) [@edeak](https://discuss.elastic.co/u/edeak)\
**Post date:** [April 1, 2016, 12:40pm UTC](https://discuss.elastic.co/t/elasticsearch-allows-only-get-requests/46059/1 "2016-04-01T12:40:21Z")

</div>

Hi guys,

two days ago I upgraded my ES cluster to the latest 2.3.0 version.  
Today somehow the cluster started to refuse all POST, PUT, DELETE requests, and allows only GET requests.  
I use postman to play with the API and I've never seen this before.

I asked our IT guys about what if they messed up some firewall settings but they sad they did nothing.

What can I do now?

---

<div class="post-metadata">

**Author:** ![edeak](https://avatars.discourse-cdn.com/v4/letter/e/a698b9/32.png) [@edeak](https://discuss.elastic.co/u/edeak)\
**Post date:** [April 1, 2016, 4:19pm UTC](https://discuss.elastic.co/t/elasticsearch-allows-only-get-requests/46059/2 "2016-04-01T16:19:30Z")

</div>

Problem was at my client node config: "http.cors.enabled" option has to be deleted.  
More details here: [https://github.com/elastic/kibana/issues/6719](https://github.com/elastic/kibana/issues/6719)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:03pm UTC](https://discuss.elastic.co/t/elasticsearch-allows-only-get-requests/46059/3 "2017-07-05T23:03:11Z")

</div>