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
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ res.setHeader('etag', '1')
102
102
This will enable browser clients to keep a copy of the cache on their side, but still being forced to validate
103
103
the cache state on the server before using the cached response, therefore supporting gateway based cache invalidation.
104
104
105
-
> NOTE: In order to fetch the generated `Cache-Control` and `ETag` headers, there have to be at least cache hit.
105
+
> NOTE: In order to fetch the generated `Cache-Control` and `ETag` headers, there have to be at least one cache hit.
106
106
107
107
### Invalidating caches
108
108
Services can easily expire cache entries on demand, i.e: when the data state changes. Here we use the `x-cache-expire` header to indicate the cache entries to expire using a matching pattern:
0 commit comments