Skip to content

Commit 8ba02f0

Browse files
nenizeraRebeccaTamachiro
authored andcommitted
[Cache]Update etag-headers.mdx (#20719)
I understand this first paragraph is an introduction to ETags headers, and its second part is explaining ETags in the context of using Cloudflare. To avoid confusion, can we use origin web server in both places here?
1 parent 1da4042 commit 8ba02f0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/cache/reference/etag-headers.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: Using ETag Headers with Cloudflare
55

66
---
77

8-
ETag headers identify whether the version of a resource cached in the browser is the same as the resource at the web server. A visitor's browser stores ETags. When a visitor revisits a site, the browser compares each ETag to the one it stored. Matching values cause a `304 Not-Modified HTTP` response that indicates the cached resource version is current. Cloudflare supports both strong and weak ETags configured at your origin web server.
8+
ETag headers identify whether the version of a resource cached in the browser is the same as the resource at the origin web server. A visitor's browser stores ETags. When a visitor revisits a site, the browser compares each ETag to the one it stored. Matching values cause a `304 Not-Modified HTTP` response that indicates the cached resource version is current. Cloudflare supports both strong and weak ETags configured at your origin web server.
99

1010
## Weak ETags
1111

0 commit comments

Comments
 (0)