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.
Requesting a large amount of components at once from the CmsService is failing
See original GitHub issue-
Description: In my project I have a very large navigation tree. Once the CategoryNavigationComponent/NavigationService try to retrieve the navigation-node-components, all the requests are sent to the CmsService at once. The call to the backend then looks like this:
/cms/components?fields=DEFAULT¤tPage=0&pageSize=713&componentIds=<huge_list_of_components>Which results in a server error: Status Code: 431 Request Header Fields Too Large -
Library version: 3.4
-
Screenshot:
-
OS: Windows
-
Browser: chrome
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (10 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
Can be resolved by updating the
findComponentsByIdsto split the request in multiple parts. Talk to me about the implementation details.Confirmed with Wei that when it’s -ve, then no ids are retrieved, thus nothing is loaded.