Set a maximum length for a dynamic route segment (slug)

[SSbit01]

Goals

1. Set a maximum length for a dynamic route segment
2. If the segment exceeds the maximum length, return a 404 or 414 page without incurring server-side rendering requests (in serverless environments).

Non-Goals

No response

Background

It could be very useful for social networks built with Next.js, especially in serverless environments where there is a price per request for server-side rendering.

Usernames typically have a maximum length of 32 characters, so there is no point in incurring a server-side rendering request if the segment is longer than 32 characters.

I'm aware that in Node.js this might not be possible, but it would be a nice feature for the edge runtime.

The only current alternative is to generate a server-side processing request and return an HTTP response status code of 404 or 414.

Proposal

I think a good implementation might be to specify operators in the segment name:

/app
  |- user
        |- [username<=32]
              |- page.jsx
              ...