Fix client-side errors caused by cached prefetch requests #442
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://github.com/vercel/next.js/blob/canary/packages/next/server/next-server.ts#L1996
This code shows that when the client sends a request with an
x-middleware-prefetch
header, the server will return an empty JSON object with anx-middleware-skip
header. If we cache these requests, will cause client error when doing client side render. We need to skip these requests when caching.