# Escaping user input for search queries

**URL:** <https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526>\
**Category:** Elasticsearch\
**Created:** [July 21, 2019, 2:38pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526 "2019-07-21T14:38:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![DevStack](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@DevStack](https://discuss.elastic.co/u/DevStack)\
**Post date:** [July 21, 2019, 2:38pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526/1 "2019-07-21T14:38:00Z")

</div>

In mysql/mariadb you have the escape\_string for making user input search strings more secure.

What is the best way to escape user input or make the user input safer when searching with match and match\_all and taking user input ?

is there a good way to escape user input and make it more secure?

---

<div class="post-metadata">

**Author:** ![DevStack](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@DevStack](https://discuss.elastic.co/u/DevStack)\
**Post date:** [July 21, 2019, 2:39pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526/2 "2019-07-21T14:39:29Z")

</div>

There is a way not to report error messages with [https://www.elastic.co/guide/en/elasticsearch/reference/1.7/query-dsl-simple-query-string-query.html](https://www.elastic.co/guide/en/elasticsearch/reference/1.7/query-dsl-simple-query-string-query.html)

but i am looking for a good way to make user input more secure

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 21, 2019, 2:55pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526/3 "2019-07-21T14:55:22Z")

</div>

Do you have an example of something unsecured?

---

<div class="post-metadata">

**Author:** ![DevStack](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@DevStack](https://discuss.elastic.co/u/DevStack)\
**Post date:** [July 21, 2019, 3:01pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526/4 "2019-07-21T15:01:06Z")

</div>

No i do not, but it is scary to have no escaping or sanitization for user input

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 21, 2019, 6:47pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526/5 "2019-07-21T18:47:28Z")

</div>

So why do you think it's unsecured then?

---

<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:** [August 18, 2019, 6:47pm UTC](https://discuss.elastic.co/t/escaping-user-input-for-search-queries/191526/6 "2019-08-18T18:47:43Z")

</div>

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