# Preventing too\_long\_frame\_exception on GetAlias Rest client

**URL:** <https://discuss.elastic.co/t/preventing-too-long-frame-exception-on-getalias-rest-client/272917>\
**Category:** Elasticsearch\
**Tags:** language-clients\
**Created:** [May 13, 2021, 2:24pm UTC](https://discuss.elastic.co/t/preventing-too-long-frame-exception-on-getalias-rest-client/272917 "2021-05-13T14:24:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amishar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amishar/32/76363_2.png) [@amishar](https://discuss.elastic.co/u/amishar)\
**Post date:** [May 13, 2021, 2:24pm UTC](https://discuss.elastic.co/t/preventing-too-long-frame-exception-on-getalias-rest-client/272917/1 "2021-05-13T14:24:16Z")

</div>

We are on Elasticsearch 6.8 and recently start using rest client. Some of the rest API endpoints like getAlias(\_alias) requests are GET requests with index names are included in the URL. When there are too many indices, the request fails with `too_long_frame_exception`. I know that we can configure the `http.max_initial_line_length`. We have thousands of indices and we need to call getAlias on all existing indices.  
Is there a getAlias POST endpoint where we can pass the index names as the body of the request instead of url path? When it is not possible to configure the ES server, we have to resort to making multiple GET requests with small batches of index names.

---

<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:** [June 10, 2021, 2:24pm UTC](https://discuss.elastic.co/t/preventing-too-long-frame-exception-on-getalias-rest-client/272917/2 "2021-06-10T14:24:22Z")

</div>

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