fix: disable hydration HTTP transfer cache #1635
Merged
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.
PR Type
[X] Application / infrastructure changes
What Is the Current Behavior?
The introduction of SSR hydration with the last Angular Upgrade also activated HTTP Cache transfer which is not desired in all cases. The PWA version before was designed to specifically refetch certain resources when booting up on the client (i.e. CMS and Product Data).
What Is the New Behavior?
HTTP Client Cache is disabled again.
Does this PR Introduce a Breaking Change?
[ ] Yes
[X] No
Other Information
AB#95994