# HTTP 414 Response with GraphQL API **URL:** \ **Category:** Developing with Prismic\ **Tags:** graphql\ **Created:** [December 15, 2020, 5:00pm UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208 "2020-12-15T17:00:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dev11](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@dev11](https://community.prismic.io/u/dev11)\ **Post date:** [December 15, 2020, 5:00pm UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208/1 "2020-12-15T17:00:43Z")
We keep receiving a 414 http response when we attempt to query the document. Our site keeps erroring out as a result. ---
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [December 15, 2020, 11:56pm UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208/2 "2020-12-15T23:56:01Z")
Hey, welcome to the community! This usually happens when the query is too long. Could you share with me the url of your repo and the query? you can send them over to me via dm if you prefer. ---
**Author:** ![dev11](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@dev11](https://community.prismic.io/u/dev11)\ **Post date:** [December 16, 2020, 12:12am UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208/4 "2020-12-16T00:12:58Z")
Hi Paulina, we were able to debug it and it was query size; however, it seems very surprising that there would be a limit on query size, especially such a strict one. We have about 15 slices for that page. That seems quite reasonable. We had to do some hacks where we split the query into 4 different queries, each fetching a subset of slices and then merging it all together. This is a very suboptimal option and I think it would be reasonable to support POST requests for graphql queries. We've had to do numerous workaround since prismic doesn't support POST. Everyone else seems to have consolidated on POST and most graphql tooling assumes POST. Are there plans to support POST requests? Also, can you please shed some light on why prismic uses GET? ---
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [December 16, 2020, 1:50am UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208/5 "2020-12-16T01:50:15Z")
Yes! Supporting POST requests is something that we discuss here and have plans to implement when we begin our improvements to the GraphQL API: > [@413 Request Entity Too Large](https://community.prismic.io/t/413-request-entity-too-large/1034): > > Hi, So it looks like at a certain point you will get a "413 Request Entity Too Large" when using graphQl with a GET request. The URI becomes massive if you have a lot of fragments and in turn slices and eventually you will hit a server limit. I managed to shave 50% off my URI string by minifying my graphql query strings and stripping out white space etc but i'm worried about the future. Is there anything that can be done to overcome this? ---
**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/system/32/1746_2.png) [@system](https://community.prismic.io/u/system)\ **Post date:** [December 22, 2020, 5:53pm UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208/6 "2020-12-22T17:53:25Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed. ---
**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/system/32/1746_2.png) [@system](https://community.prismic.io/u/system)\ **Post date:** [December 9, 2021, 4:49pm UTC](https://community.prismic.io/t/http-414-response-with-graphql-api/3208/7 "2021-12-09T16:49:27Z")