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
At the moment the etag of the layout service with be used directly for the response of the service side rendered html-page for the result. But when the code is changed (after deployment), the same etag will be delivered, when the sitecore data hasn't been changed, but the html can be totally different because of the new code. this will lead to some caching issues, when the html is cached by the cdn or browser (cache-control).
Expected behavior
no etag for the rendered html response
or
a new generated etag for the html from the serverside rendering.
Steps To Reproduce
Possible Fix
Your Environment
Sitecore Version: 10.1
JSS Version: 18.0.1
Browser Name and version: not relevant
Operating System and version (desktop or mobile): Windows 10
The text was updated successfully, but these errors were encountered:
Description
At the moment the etag of the layout service with be used directly for the response of the service side rendered html-page for the result. But when the code is changed (after deployment), the same etag will be delivered, when the sitecore data hasn't been changed, but the html can be totally different because of the new code. this will lead to some caching issues, when the html is cached by the cdn or browser (cache-control).
Expected behavior
no etag for the rendered html response
or
a new generated etag for the html from the serverside rendering.
Steps To Reproduce
Possible Fix
Your Environment
The text was updated successfully, but these errors were encountered: