cloudflare · Oxyjun · May 6, 2026 · May 7, 2026 · May 7, 2026
@@ -9,41 +9,36 @@ tags:
   - Security
 ---
 
-The Child Sexual Abuse Material (CSAM) Scanning Tool allows website owners to proactively identify and take action on CSAM located on their website. By enabling this tool, Cloudflare will compare content served for your website through the Cloudflare cache to known lists of CSAM. These lists are provided to Cloudflare by leading child safety advocacy groups such as the National Center for Missing and Exploited Children (NCMEC).
+import { DashButton } from "~/components";
 
-Remember, by enabling the Service, you agree to the [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-application-services/#csam-scanning-tool-terms) for the CSAM Scanning Tool. You agree to use this tool solely for the purposes of preventing the spread of CSAM.
+The Child Sexual Abuse Material (CSAM) Scanning Tool allows website owners to proactively identify and take action on CSAM present on their website. When you turn on this tool, Cloudflare compares content served for your website through the Cloudflare cache to known lists of CSAM. These lists are provided by leading child safety advocacy groups such as the National Center for Missing and Exploited Children (NCMEC).
 
----
-
-## Why would a URL be blocked?
+By turning on the Service, you agree to the [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-application-services/#csam-scanning-tool-terms) for the CSAM Scanning Tool. You agree to use this tool solely for the purposes of preventing the spread of CSAM.
 
-Because knowingly distributing or viewing CSAM is illegal, the owner of the website has enabled Cloudflare's CSAM scanning tool to proactively identify and block images identified as CSAM located on their website.
+## Blocked URLs
 
----
+Because knowingly distributing or viewing CSAM is illegal, the owner of the website has turned on Cloudflare's CSAM scanning tool to proactively identify and block images identified as CSAM on their website.
 
 ## Configure the CSAM scanning tool
 
-To enable the tool:
+To turn on the tool:
 
-1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. Select your account and zone.
-3. Go to **Caching** > **Configuration**.
-4. For **CSAM Scanning Tool**, select **Configure**.
+1. Log the Cloudflare dashboard, select your account and domain, and go to **Caching** > **Configuration**.
 
-You must provide an email address, which will be used to notify you in the event Cloudflare detects a positive match.
+   <DashButton url="/?to=/:account/:zone/caching/configuration" />
 
----
+2. Go to **CSAM Scanning Tool**, then select **Configure**.
+
+You must provide an email address, which Cloudflare uses to notify you if a positive match is detected.
 
-## What happens when a match is detected?
+## Match detection behavior
 
 When a potential match is detected with the tool:
 
-1. An email is sent to you once per day to inform you of any detections made in the past 24 hours. This email will include the file paths of any content that was matched.
-2. If possible, a block is placed to prevent further serving of the matched content. If a block fails, we will indicate that the content has not been blocked in the email.
+1. Cloudflare sends you an email once per day to inform you of any detections made in the past 24 hours. This email includes the file paths of any content that was matched.
+2. If possible, Cloudflare places a block to prevent further serving of the matched content. If a block fails, the email indicates that the content has not been blocked.
 
----
-
-## What action should I take when a match is detected?
+## Required actions after a match
 
 You are responsible for understanding and complying with any legal obligations you have as a website owner when made aware of any potential CSAM. Although legal obligations vary based on the provider and the jurisdiction, website owners often have obligations to report apparent CSAM, to remove content, and to preserve records. Some of those possible obligations are as follows:
 
@@ -57,11 +52,9 @@ You are responsible for understanding and complying with any legal obligations y
 <br />
 
 - You should remove the content and notify Cloudflare of the removal.
-- Once any preservation obligations have been fulfilled, you should remove the content from your website. This is especially important if Cloudflare's notice to you indicates that our block was unsuccessful.
-
----
+- Once any preservation obligations have been fulfilled, you should remove the content from your website. This is especially important if the notification from Cloudflare indicates that the block was unsuccessful.
 
-## How do I have a block removed from my website?
+## Remove a block from your website
 
 To disable a block, either because you have determined that the blocked content is not CSAM (a false positive) or because you have taken down the blocked content, view [Blocked Content in the Security Center](/fundamentals/reference/report-abuse/blocked-content/) in the Cloudflare Dashboard and request reviews on the relevant blocks. A request to remove a block must be accompanied by a representation from you confirming that the blocked content is not CSAM or has been removed.
 
@@ -71,9 +64,7 @@ These actions are available to users with the following roles:
 - Super Admin
 - Trust & Safety
 
----
-
-## Additional Resources
+## Additional resources
 
 [CSAM Scanning Tool Supplemental Terms](https://www.cloudflare.com/supplemental-terms/)
 

@@ -9,7 +9,7 @@ products:
 
 import { DashButton } from "~/components"
 
-Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) features for three hours unless disabled beforehand. Development Mode allows customers to immediately observe changes to their [cacheable content](/cache/concepts/default-cache-behavior/#default-cached-file-extensions) like images, CSS, or JavaScript.
+Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) (image optimization) for three hours unless disabled beforehand. This allows you to immediately observe changes to your [cacheable content](/cache/concepts/default-cache-behavior/#default-cached-file-extensions) like images, CSS, or JavaScript without waiting for cached versions to expire.
 
 :::note
 
@@ -20,7 +20,7 @@ To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/
 
 Development Mode temporarily bypasses Cloudflare's cache and does not purge cached files. To instantly purge your Cloudflare cache, refer to [purge cache](/cache/how-to/purge-cache/).
 
-1. In the Cloudflare dashboard, go to the **Configuration** page.
+1. Log in to the Cloudflare dashboard and select your account and domain. Go to the **Configuration** page.
 
    <DashButton url="/?to=/:account/:zone/caching/configuration" />
 

@@ -8,11 +8,11 @@ title: Using ETag Headers with Cloudflare
 
 ---
 
-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.
+ETag (Entity Tag) 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, so the browser can use its local copy instead of downloading the resource again. Cloudflare supports both strong and weak ETags configured at your origin web server.
 
 ## Weak ETags
 
-Weak ETag headers indicate a cached resource is semantically equivalent to the version on the web server but not necessarily byte-for-byte identical.
+Weak ETag headers indicate a cached resource is semantically equivalent to the version on the web server but not necessarily byte-for-byte identical. For example, the content may be the same but compressed differently or have minor formatting differences.
 
 :::note
 
@@ -30,7 +30,7 @@ Strong ETag headers ensure the resource in browser cache and on the web server a
 
 When you enable **Respect Strong ETags** in a cache rule, Cloudflare will use strong ETag header validation to ensure that resources in the Cloudflare cache and on the origin server are byte-for-byte identical.
 
-However, in some situations Cloudflare will convert strong ETags to weak ETags. For example, given the following conditions:
+However, in some situations Cloudflare will convert strong ETags to weak ETags. This happens when Cloudflare must decompress and recompress a response to match what the visitor's browser accepts — because the bytes change during recompression, the ETag can no longer guarantee a byte-for-byte match. For example, given the following conditions:
 
 * **Respect Strong ETags** is enabled
 * [Brotli compression](/speed/optimization/content/compression/) is enabled
@@ -53,7 +53,7 @@ The Cloudflare network will take the following actions, depending on the visitor
 
 </table-wrap>
 
-Enabling **Respect Strong ETags** in Cloudflare automatically disables Rocket Loader, Email Obfuscation, and Automatic HTTPS Rewrites.
+Enabling **Respect Strong ETags** in Cloudflare automatically disables [Rocket Loader](/speed/optimization/content/rocket-loader/), [Email Obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/), and [Automatic HTTPS Rewrites](/ssl/edge-certificates/additional-options/automatic-https-rewrites/).
 
 ### Behavior with Respect Strong ETags disabled
 
@@ -92,6 +92,6 @@ Refer to [Content compression](/speed/optimization/content/compression/) for mor
 
 * You must set the value in a strong ETag header using double quotes (for example, `etag: "foobar"`). If you use an incorrect format, Cloudflare will remove the ETag header instead of converting it to a weak ETag. 
 
-* 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 a resource is cacheable and there is a [cache miss](/cache/concepts/cache-responses/#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.