[Partial Prefetching] Don't report vary params in responses that include dynamic data (#99700)
A navigation response that includes dynamic data should not report any vary params, because (until the Ledgers feature lands in React), we cannot track params during a streaming render. This updates the server to send `null`, which represents an unknown set of params. The previous structure was mostly harmless because the client only uses the vary params when writing to its local cache, and navigation responses are not written to the cache (except when they are fully static). The one exception is when performing a full prefetch when Partial Prefetching is not enabled — the client had a special case to ignore the (bogus) vary params sent by the server and treat them as unknown. The special case is no longer necessary after this fix. Now the server's vary params can be treated as authoritative in all cases without special handling on the client.
Showing
Please
register
or
sign in
to comment