Populate URI is too long (throws 414 error). Is there a better way?

Discord Q&A strapi-questions
1

I’m using the strapi/next-corportate-starter (GitHub - strapi/nextjs-corporate-starter: Strapi Demo application for Corporate Websites using Next.js) Gituhb template to build a client website. All the website’s page data is fetched from Strapi (seo, sections, etc).

In production, when I try to fetch the page data using the REST API, I get a 414 URI Too Long. Think it’s because the request query string is extremely long (see image).

Apparently, this is a limit on the server level (ex: Apache’s LimitRequestLine core - Apache HTTP Server Version 2.2).

While I’m looking into changing it, I’m wondering if there’s a better way to fetch the data. Even if I change the limit, I could run into the same issue if I add another page that requests any more data. The client doesn’t have the appetite to do a big rewrite to migrate to something like GraphQL, but open to it if that’s the only way.

Thanks!

This topic has been created from a Discord post (1255254469655134259) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

2

Yea we hardcode populates on backend

3
4

You can check my starter it uses redux with hydration

5

<@632956853122236457> Gotcha, thanks for sharing this, much appreciated!

6

<@632956853122236457> Looked through the repo but struggled to find where you’re hardcoding the populates. Mind pointing me to the right spot?