You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering how to maintain same _rsc key for links across the pages. Below are example,
In page - example.com/about - the _rsc key for that contact page will be "HYFGB", example link below
example.com/contact?_rsc=HYFGB
In Page - example.com/story - the key for that story page will be "AKYGV", example link below
example.com/contact?_rsc=AKYGV
In the above example the _rsc key of contact page is different in about and story pages. This leads to fetch the rsc pages of same link multiple times in different pages when it is behind CDN.
I am expecting to use same _rsc=XXXX key across all the pages for the links.
I'm bringing up this problem because every page has a unique _rsc key, which means the requests cached on the CDN are not very effective. For websites with over 100,000 pages, each page has more than 300 links and when around 100 _rsc hits the server simultaneously the takes bit longer to responds approximately 2 to 5 seconds under high traffic conditions like 1k concurrent users. This delay makes the website seem unresponsive to users when they click on any link.
The text was updated successfully, but these errors were encountered:
I was wondering how to maintain same _rsc key for links across the pages. Below are example,
In the above example the _rsc key of contact page is different in about and story pages. This leads to fetch the rsc pages of same link multiple times in different pages when it is behind CDN.
I am expecting to use same _rsc=XXXX key across all the pages for the links.
I'm bringing up this problem because every page has a unique _rsc key, which means the requests cached on the CDN are not very effective. For websites with over 100,000 pages, each page has more than 300 links and when around 100 _rsc hits the server simultaneously the takes bit longer to responds approximately 2 to 5 seconds under high traffic conditions like 1k concurrent users. This delay makes the website seem unresponsive to users when they click on any link.
The text was updated successfully, but these errors were encountered: