JJ KasperandGitHub d4f5368f2c Update RSC etag generation handling (#63336) ...

Currently when we generate payloads in app router, the order of RSC
chunks aren't deterministic even if the content stays the same. This
means that any caches that rely on etags for detecting changes in
content aren't able to reliably cache/and avoid invalidating properly.
To avoid this we can manually sort the content before generating the
etag. Eventually this can be fixed upstream in react although that is a
bigger lift so we are doing this for now to alleviate the issue.

x-ref: [slack
thread](https://vercel.slack.com/archives/C042LHPJ1NX/p1709937748240119?thread_ts=1709856182.174879&cid=C042LHPJ1NX)

Closes NEXT-2825

2024-03-19 21:45:21 +00:00

..

revalidate-3

Update RSC etag generation handling (#63336)

2024-03-19 21:45:21 +00:00