# Percolator match queries not working with http GET with body **URL:** \ **Category:** Elasticsearch\ **Created:** [June 30, 2016, 11:20pm UTC](https://discuss.elastic.co/t/percolator-match-queries-not-working-with-http-get-with-body/54479 "2016-06-30T23:20:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![redtopia](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@redtopia](https://discuss.elastic.co/u/redtopia)\ **Post date:** [June 30, 2016, 11:20pm UTC](https://discuss.elastic.co/t/percolator-match-queries-not-working-with-http-get-with-body/54479/1 "2016-06-30T23:20:42Z")
Using Elasticsearch 2.3 - my JVM app server doesn't support sending a body with a http GET request. According to the percolator documentation: [https://www.elastic.co/guide/en/elasticsearch/reference/current/search-percolate.html#\_sample\_usage](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-percolate.html#_sample_usage) when I want to match documents against registered queries, I need to send my query in with the body of a GET http request. I need to find a workaround... is there another way to send in my document? Also, the Head plugin doesn't work either... when I try to test my queries, Head basically sends my query as a queryparam in my url, which generates an error: "type": "illegal\_argument\_exception", "reason": "Nothing to percolate" So, right now I'm dead in the water. I added all my percolator queries, and now I have no way to either test them (using Head) or access them from my server (web app). ---
**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\ **Post date:** [July 1, 2016, 7:22am UTC](https://discuss.elastic.co/t/percolator-match-queries-not-working-with-http-get-with-body/54479/2 "2016-07-01T07:22:39Z")
The percolate api also support http post. Have you tried that? ---
**Author:** ![redtopia](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@redtopia](https://discuss.elastic.co/u/redtopia)\ **Post date:** [July 1, 2016, 4:00pm UTC](https://discuss.elastic.co/t/percolator-match-queries-not-working-with-http-get-with-body/54479/3 "2016-07-01T16:00:18Z")
Yes, POST seems to work... I didn't think so at first because I wasn't getting any results back and it took a very long time, I guess I need to tighten up my queries so they're not so expensive. It took 31 seconds to search 5000 queries. Does that seem right? ---
**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\ **Post date:** [July 4, 2016, 6:43am UTC](https://discuss.elastic.co/t/percolator-match-queries-not-working-with-http-get-with-body/54479/4 "2016-07-04T06:43:29Z")
Depending of the complexity of the document you're percolating, your percolator queries and the resources of your cluster this is possible. The upcoming ES 5 release can perhaps improve your performance: > **[Elasticsearch Percolator Continues to Evolve](https://www.elastic.co/blog/elasticsearch-percolator-continues-to-evolve)** > > In Elasticsearch 5.0 the percolator is much more flexible and has many improvements. For example, to be able to skip evaluating most queries. ---
**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, 10:38pm UTC](https://discuss.elastic.co/t/percolator-match-queries-not-working-with-http-get-with-body/54479/5 "2017-07-05T22:38:38Z")