# Scan and Scroll : URI length exceeds the configured limit **URL:** \ **Category:** Elasticsearch\ **Created:** [December 23, 2015, 11:46am UTC](https://discuss.elastic.co/t/scan-and-scroll-uri-length-exceeds-the-configured-limit/37851 "2015-12-23T11:46:17Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![voipoclay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/voipoclay/32/4372_2.png) [@voipoclay](https://discuss.elastic.co/u/voipoclay)\ **Post date:** [December 23, 2015, 2:34pm UTC](https://discuss.elastic.co/t/scan-and-scroll-uri-length-exceeds-the-configured-limit/37851/3 "2015-12-23T14:34:10Z")
Check out my post here > [@Scan and Scroll 100 Index Limit](https://discuss.elastic.co/t/scan-and-scroll-100-index-limit/29819/4): > > found the answer to my own question. Following the api at the following link [https://www.elastic.co/guide/en/elasticsearch/client/php-api/current/\_search\_operations.html#\_scan\_scroll](https://www.elastic.co/guide/en/elasticsearch/client/php-api/current/_search_operations.html#_scan_scroll) ... I found that using scroll\_id in the URI became too long in the while loop so it didn't work once indices reached a certain size. Specifying it the way the docs say to makes it a GET request and therefore eventually truncates the request URI. I just removed it and made the body attribute the scroll\_id and then … Hope this helps --- _[View the full topic](https://discuss.elastic.co/t/scan-and-scroll-uri-length-exceeds-the-configured-limit/37851)._