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

angelampcosta · marciocloudflare · web-flow · commit 1f655f2df0cd · 2025-10-02T10:07:29.000+01:00
Co-authored-by: marciocloudflare &lt;83226960+marciocloudflare@users.noreply.github.com&gt;
diff --git a/src/content/docs/cache/reference/etag-headers.mdx b/src/content/docs/cache/reference/etag-headers.mdx
@@ -83,4 +83,4 @@ The Cloudflare network will take the following actions, depending on the visitor
 
 * If a resource is cacheable and there is a cache miss, Cloudflare does not send ETag headers to the origin server. This is because Cloudflare requires the full response body to fill its cache.
 
-* If your Origin (or R2) applies compression based on `accept-encoding`, the first compression type will be cached. Consider whether strong ETags fit your use case, or use cache key rules to handle different compression types.
+* If your origin (or R2) applies compression based on `accept-encoding`, the first compression type will be cached. Consider whether strong ETags fit your use case, or use cache key rules to handle different compression types.

Original file line number	Diff line number	Diff line change
`@@ -83,4 +83,4 @@ The Cloudflare network will take the following actions, depending on the visitor`
`83`	`83`
`84`	`84`	`* If a resource is cacheable and there is a cache miss, Cloudflare does not send ETag headers to the origin server. This is because Cloudflare requires the full response body to fill its cache.`
`85`	`85`
`86`		-* If your Origin (or R2) applies compression based on `accept-encoding`, the first compression type will be cached. Consider whether strong ETags fit your use case, or use cache key rules to handle different compression types.
	`86`	+* If your origin (or R2) applies compression based on `accept-encoding`, the first compression type will be cached. Consider whether strong ETags fit your use case, or use cache key rules to handle different compression types.