Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Request-URI Too Long
See original GitHub issueMy team is using GraphiQL and loving it! Thank you for such an awesome tool.
Recently we have been receiving the following error on our longer queries:
Request-URI Too Long
The requested URL's length exceeds the capacity limit for this server.
I narrowed it down to Apache rejecting the URL:
However, our Infrastructure team will not increase the character count max for Apache stating:
There is a 2k character count max for most browsers, servers, etc. You have a URL with 12859 characters.
Is there anything we can do to reduce the URL character count? Thanks in advance!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You understand my situation correctly.
I will need time to investigate your proposed workaround. Thank you for your support!
@michaelcurry Hi there! Basically you would map an unique key to a query string (and probably also variables) and store the combination in the server. There isn’t an official documentation as far as I know about this topic since it’s one of the advanced topics, but I’ve found a helpful guide to get you started - https://dev-blog.apollodata.com/persisted-graphql-queries-with-apollo-client-119fd7e6bba5
The above link is closely tied with JavaScript/Apollo tools, but it’d be useful to give you a basic understanding of how a persisted query would be created. Let me know if you have other questions about it please.