# Why does action.destructive\_requires\_name doesn't work for

**URL:** <https://discuss.elastic.co/t/why-does-action-destructive-requires-name-doesnt-work-for/16252>\
**Category:** Elasticsearch\
**Created:** [March 9, 2014, 11:20am UTC](https://discuss.elastic.co/t/why-does-action-destructive-requires-name-doesnt-work-for/16252 "2014-03-09T11:20:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![theGhost](https://avatars.discourse-cdn.com/v4/letter/t/cdc98d/32.png) [@theGhost](https://discuss.elastic.co/u/theGhost)\
**Post date:** [March 9, 2014, 11:20am UTC](https://discuss.elastic.co/t/why-does-action-destructive-requires-name-doesnt-work-for/16252/1 "2014-03-09T11:20:19Z")

</div>

I accidentally deleted all indexes, due to this serious interface flaw of elasticsearch.  
I issued a CURL delete request on http://:9200 & all my indexes were lost.

Why would elasticsearch entertain such a destructive request so seamlessly, on the entire cluster ??!!  
Then I added:  
action.destructive\_requires\_name: true, mapping in config/elasticsearch.yml & again issued DELETE on a local cluster, & to shame it deleted all indices !! (Guess the config only restricts DELETE request issued on /\_all urls)

Thanks,  
Durga

---

<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 6, 2017, 1:44am UTC](https://discuss.elastic.co/t/why-does-action-destructive-requires-name-doesnt-work-for/16252/2 "2017-07-06T01:44:37Z")

</div>