The two statuses identify different points in the eligibility decision.
\nCloudflare documents DYNAMIC as ineligible for cache at request time, such as an unmatched HTML response or an explicit bypass rule. BYPASS means the request was eligible but the response was not cacheable. MISS describes eligible content absent at lookup time. The source also notes that an Age header can originate upstream on an uncacheable response, so it is not conclusive by itself.
\nSource: Cloudflare — Cloudflare cache responses.
\nThis concerns Cloudflare CDN response diagnostics.
\nDSE recommends starting with the request’s eligibility rules when the result is DYNAMIC and examining response directives, cookies, and limits when it is BYPASS. Capture the exact URL, method, relevant headers, rule matches, and timestamp. Do not change several TTL settings before locating the decision stage. Keep Workers, redirects, and WAF-generated responses in view because they can occur before an ordinary cache lookup. Keep a small diagnostic worksheet with separate request-eligibility and response-cacheability columns. Populate it for one DYNAMIC and one BYPASS example before changing configuration. Trace the Age header to its producer rather than using its presence to overrule the more specific cache-status evidence.
\nRepeat a controlled request for an intentionally cacheable test asset and compare the initial and subsequent statuses. Compare it with a deliberately uncached endpoint and inspect origin headers. Record which stage explains each result, and validate the page content separately from the cache-status investigation.
\nCloudflare — Cloudflare cache responses. Reviewed October 20, 2026.
", "content_text": "The two statuses identify different points in the eligibility decision.\nSource facts\nCloudflare documents DYNAMIC as ineligible for cache at request time, such as an unmatched HTML response or an explicit bypass rule. BYPASS means the request was eligible but the response was not cacheable. MISS describes eligible content absent at lookup time. The source also notes that an Age header can originate upstream on an uncacheable response, so it is not conclusive by itself.\nSource: Cloudflare — Cloudflare cache responses.\nApplicability\nThis concerns Cloudflare CDN response diagnostics.\nDSE recommendation\nDSE recommends starting with the request’s eligibility rules when the result is DYNAMIC and examining response directives, cookies, and limits when it is BYPASS. Capture the exact URL, method, relevant headers, rule matches, and timestamp. Do not change several TTL settings before locating the decision stage. Keep Workers, redirects, and WAF-generated responses in view because they can occur before an ordinary cache lookup. Keep a small diagnostic worksheet with separate request-eligibility and response-cacheability columns. Populate it for one DYNAMIC and one BYPASS example before changing configuration. Trace the Age header to its producer rather than using its presence to overrule the more specific cache-status evidence.\nVerification\nRepeat a controlled request for an intentionally cacheable test asset and compare the initial and subsequent statuses. Compare it with a deliberately uncached endpoint and inspect origin headers. Record which stage explains each result, and validate the page content separately from the cache-status investigation.\nOfficial reference\nCloudflare — Cloudflare cache responses. Reviewed October 20, 2026.", "content_markdown": "The two statuses identify different points in the eligibility decision.\n\n## Source facts\n\nCloudflare documents DYNAMIC as ineligible for cache at request time, such as an unmatched HTML response or an explicit bypass rule. BYPASS means the request was eligible but the response was not cacheable. MISS describes eligible content absent at lookup time. The source also notes that an Age header can originate upstream on an uncacheable response, so it is not conclusive by itself.\n\nSource: [Cloudflare — Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/).\n\n## Applicability\n\nThis concerns Cloudflare CDN response diagnostics.\n\n## DSE recommendation\n\nDSE recommends starting with the request’s eligibility rules when the result is DYNAMIC and examining response directives, cookies, and limits when it is BYPASS. Capture the exact URL, method, relevant headers, rule matches, and timestamp. Do not change several TTL settings before locating the decision stage. Keep Workers, redirects, and WAF-generated responses in view because they can occur before an ordinary cache lookup. Keep a small diagnostic worksheet with separate request-eligibility and response-cacheability columns. Populate it for one DYNAMIC and one BYPASS example before changing configuration. Trace the Age header to its producer rather than using its presence to overrule the more specific cache-status evidence.\n\n## Verification\n\nRepeat a controlled request for an intentionally cacheable test asset and compare the initial and subsequent statuses. Compare it with a deliberately uncached endpoint and inspect origin headers. Record which stage explains each result, and validate the page content separately from the cache-status investigation.\n\n## Official reference\n\n[Cloudflare — Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/). Reviewed October 20, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/", "url": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-20" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Cybersecurity", "item": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "ListItem", "position": 3, "name": "Distinguish Cloudflare DYNAMIC from BYPASS before troubleshooting an uncached URL", "item": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/#article", "identifier": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/", "url": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/", "headline": "Distinguish Cloudflare DYNAMIC from BYPASS before troubleshooting an uncached URL", "description": "The two statuses identify different points in the eligibility decision.", "abstract": "The two statuses identify different points in the eligibility decision.", "articleBody": "The two statuses identify different points in the eligibility decision.\nSource facts\nCloudflare documents DYNAMIC as ineligible for cache at request time, such as an unmatched HTML response or an explicit bypass rule. BYPASS means the request was eligible but the response was not cacheable. MISS describes eligible content absent at lookup time. The source also notes that an Age header can originate upstream on an uncacheable response, so it is not conclusive by itself.\nSource: Cloudflare — Cloudflare cache responses.\nApplicability\nThis concerns Cloudflare CDN response diagnostics.\nDSE recommendation\nDSE recommends starting with the request’s eligibility rules when the result is DYNAMIC and examining response directives, cookies, and limits when it is BYPASS. Capture the exact URL, method, relevant headers, rule matches, and timestamp. Do not change several TTL settings before locating the decision stage. Keep Workers, redirects, and WAF-generated responses in view because they can occur before an ordinary cache lookup. Keep a small diagnostic worksheet with separate request-eligibility and response-cacheability columns. Populate it for one DYNAMIC and one BYPASS example before changing configuration. Trace the Age header to its producer rather than using its presence to overrule the more specific cache-status evidence.\nVerification\nRepeat a controlled request for an intentionally cacheable test asset and compare the initial and subsequent statuses. Compare it with a deliberately uncached endpoint and inspect origin headers. Record which stage explains each result, and validate the page content separately from the cache-status investigation.\nOfficial reference\nCloudflare — Cloudflare cache responses. Reviewed October 20, 2026.", "datePublished": "2026-10-20T18:16:33+00:00", "dateModified": "2026-10-20T18:34:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/distinguish-cloudflare-dynamic-from-bypass-before-troubleshooting-an-uncached-url/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Distinguish Cloudflare DYNAMIC from BYPASS before troubleshooting an uncached URL" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 247, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Cloudflare — Cloudflare cache responses", "url": "https://developers.cloudflare.com/cache/concepts/cache-responses/" } } ] } }