Return 400 instead of 500 for unparseable Next-Router-State-Tree header
When a client sends an invalid or incompatible Next-Router-State-Tree header (e.g. cross-version same-origin navigation from Next 14 to 16), the server now returns 400 instead of 500. This is semantically correct (client sent a bad header) and avoids CDN caching of 500 responses.
Showing
Please
register
or
sign in
to comment