# Anyway that I can cancel the header \`kbn-xsrf\` verify in POST method

**URL:** <https://discuss.elastic.co/t/anyway-that-i-can-cancel-the-header-kbn-xsrf-verify-in-post-method/76141>\
**Category:** Kibana\
**Created:** [February 23, 2017, 3:54am UTC](https://discuss.elastic.co/t/anyway-that-i-can-cancel-the-header-kbn-xsrf-verify-in-post-method/76141 "2017-02-23T03:54:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![whoami](https://avatars.discourse-cdn.com/v4/letter/w/a9a28c/32.png) [@whoami](https://discuss.elastic.co/u/whoami)\
**Post date:** [February 23, 2017, 3:54am UTC](https://discuss.elastic.co/t/anyway-that-i-can-cancel-the-header-kbn-xsrf-verify-in-post-method/76141/1 "2017-02-23T03:54:04Z")

</div>

anyway that I can cancel the header `kbn-xsrf` verify in POST method? I am adding some api in my own plugin, and its nothing about kibana, so I want there is no necessary to check kbn-xsrf header

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [February 23, 2017, 3:36pm UTC](https://discuss.elastic.co/t/anyway-that-i-can-cancel-the-header-kbn-xsrf-verify-in-post-method/76141/2 "2017-02-23T15:36:01Z")

</div>

You could add the following in your config:

```
server.xsrf.disableProtection: true

```

Note that this is not recommended for production because it leaves your application open to [XSRF attacks](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)).

---

<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:** [March 23, 2017, 3:36pm UTC](https://discuss.elastic.co/t/anyway-that-i-can-cancel-the-header-kbn-xsrf-verify-in-post-method/76141/3 "2017-03-23T15:36:02Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.