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 found that when the browser provides request header "if-none-match" with etag value same as the generated content, cacheable-response doesn't save the response in cache after expired.
This causes the server executes SSR on every request because cacheable-response doesn't save the response cache.
I found that when the browser provides request header "if-none-match" with etag value same as the generated content, cacheable-response doesn't save the response in cache after expired.
This causes the server executes SSR on every request because cacheable-response doesn't save the response cache.
Should the cache saving block
cacheable-response/index.js
Lines 123 to 127 in 55eca7a
cacheable-response/index.js
Lines 117 to 121 in 55eca7a
The text was updated successfully, but these errors were encountered: