cloudflare · hyperlint-ai · Apr 30, 2025 · Apr 30, 2025 · Apr 30, 2025 · Apr 30, 2025
@@ -11,7 +11,7 @@ enable_flag: "assets_navigation_prefers_asset_serving"
 disable_flag: "assets_navigation_has_no_effect"
 ---
 
-For Workers with [static assets](/workers/static-assets/) and this compatibility flag enabled, navigation requests (requests which have a `Sec-Fetch-Mode: navigate` header) will prefer to be served by our asset-serving logic, even when an exact asset match cannot be found. This is particularly useful for applications which operate in either [Single Page Application (SPA) mode](/workers/static-assets/routing/#not_found_handling--404-page--single-page-application--none) or [404 page mode](/workers/static-assets/routing/#not_found_handling--404-page--single-page-application--none), as this now means the fallback pages of `200 /index.html` and `404 /404.html` will be served ahead of invoking a Worker script and will therefore avoid incurring a charge.
+For Workers with [static assets](/workers/static-assets/) and with this compatibility flag enabled, navigation requests (requests which have a `Sec-Fetch-Mode: navigate` header) will prioritize being served by our asset-serving logic, even when an exact asset match cannot be found.
 
 Without this flag, the runtime will continue to apply the old behavior of invoking a Worker script (if present) for any requests which do not exactly match a static asset.
 

@@ -16,7 +16,7 @@ method is specified as `get`, `post`, `put`, `delete`, `head`, or `options`,
 implementations are expected to uppercase the method. All other method names
 would generally be expected to throw as unrecognized (for example, `patch` would be
 an error while `PATCH` is accepted). This is a bit restrictive, even if it is in the spec.
-This flag modifies the behavior to uppercase all methods
+This flag ensures that all HTTP methods are uppercased
 prior to parsing so that the method is always recognized if it is a known
 method.
 

@@ -83,7 +83,7 @@ The following tables have more information on each response field.
 | `AD`               | If true, it means that every record in the answer was verified with DNSSEC.                                                                                                                                                                   |
 | `CD`               | If true, the client asked to disable DNSSEC validation. In this case, Cloudflare will still fetch the DNSSEC-related records, but it will not attempt to validate the records.                                                                |
 | `Question: name`   | The record name requested.                                                                                                                                                                                                                    |
-| `Question: type`   | The type of DNS record requested. These are defined here: [https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4).     |
+The types of DNS records requested are listed in the following resource: [https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4).
 | `Answer: name`     | The record owner.                                                                                                                                                                                                                             |
 | `Answer: type`     | The type of DNS record. These are defined here: [https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4).               |
 | `Answer: TTL`      | The number of seconds the answer can be stored in cache before it is considered stale.                                                                                                                                                        |

@@ -17,7 +17,7 @@ Below you will find answers to our most commonly asked questions. If you cannot
 
 1.1.1.1 is Cloudflare's fast and secure DNS resolver. When you request to visit an application like `cloudflare.com`, your computer needs to know which server to connect you to so that it can load the application. Computers don’t know how to do this name to address translation, so they ask a specialized server to do it for them.
 
-This specialized server is called a DNS recursive resolver. The resolver’s job is to find the address for a given name, like `2400:cb00:2048:1::c629:d7a2` for `cloudflare.com`, and return it to the computer that asked for it.
+This specialized server is called a DNS recursive resolver. The resolver's job is to find the address for a given name, like `2400:cb00:2048:1::c629:d7a2` for `cloudflare.com`, and return it to the computer that asked for it.
 
 Computers are configured to talk to specific DNS resolvers, identified by IP address. Usually the configuration is managed by your ISP (like Comcast or AT\&T) if you are on your home or wireless Internet, and by your network administrator if you’re connected to the office Internet. You can also change the configured DNS resolver your computer talks to yourself.
 
@@ -28,19 +28,19 @@ Computers are configured to talk to specific DNS resolvers, identified by IP add
 Visit [1.1.1.1/help](https://one.one.one.one/help) to make sure your system is connected to 1.1.1.1 and that it is working.
 
 
-## What do DNS resolvers do?
+## What do DNS resolvers do
 
 DNS resolvers are like address books for the Internet. They translate the name of places to addresses so that your browser can figure out how to get there. DNS resolvers do this by working backwards from the top until they find the website your are looking for.
 
 Every resolver knows how to find the invisible `.` at the end of domain names (for example, `cloudflare.com.`). There are [hundreds of root servers](http://www.root-servers.org/) all over the world that host the `.` file, and resolvers are [hard coded to know the IP addresses](http://www.internic.net/domain/named.root) of those servers. Cloudflare itself hosts [that file](http://www.internic.net/domain/root.zone) on all of its servers around the world through a [partnership with ISC](https://blog.cloudflare.com/f-root/).
 
 The resolver asks one of the root servers where to find the next link in the chain — the top-level domain (abbreviated to TLD) or domain ending. An example of a TLD is `.com` or `.org`. Luckily, the root servers store the locations of all the TLD servers, so they can return which IP address the DNS resolver should go ask next.
 
-The resolver then asks the TLD’s servers where it can find the domain it is looking for. For example, a resolver might ask `.com` where to find `cloudflare.com`. TLDs host a file containing the location of every domain using the TLD.
+The resolver then asks the TLD's servers where it can find the domain it is looking for. For example, a resolver might ask '.com' where to find 'cloudflare.com'. TLDs host a file containing the location of every domain using the TLD.
 
 Once the resolver has the final IP address, it returns the answer to the computer that asked.
 
-This whole system is called the [Domain Name System (DNS)](https://www.cloudflare.com/learning/dns/what-is-dns/). This system includes the servers that host the information (called [authoritative DNS](https://www.cloudflare.com/learning/dns/dns-server-types/)) and the servers that seek the information (the DNS resolvers).
+The Domain Name System (DNS) is a system that includes the servers hosting the information (called [authoritative DNS](https://www.cloudflare.com/learning/dns/dns-server-types/)) and the servers seeking the information (the DNS resolvers).
 
 ## Does 1.1.1.1 support ANY?
 
@@ -52,7 +52,7 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec
 1.1.1.1 is a DNSSEC validating resolver. 1.1.1.1 sends the `DO` (`DNSSEC OK`) bit on every query to convey to the authoritative server that it wishes to receive signed answers if available. 1.1.1.1 supports the signature algorithms specified in [Supported DNSKEY signature algorithms](/1.1.1.1/encryption/dnskey/).
 
 
-## Does 1.1.1.1 send EDNS Client Subnet header?
+## Does 1.1.1.1 send EDNS Client Subnet header
 
 1.1.1.1 is a privacy centric resolver so it does not send any client IP information and does not send the <GlossaryTooltip term="EDNS Client Subnet (ECS)">EDNS Client Subnet (ECS)</GlossaryTooltip> header to authoritative servers. The exception is the single Akamai debug domain `whoami.ds.akahelp.net` to aid in cross-provider debugging. However, Cloudflare does not send ECS to any of Akamai's production domains, such as `akamaihd.net` or similar.
 
@@ -62,22 +62,22 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec
 1.1.1.1 has full IPv6 support.
 
 
-## What is Purge Cache?
+## What is Purge Cache
 
 
 1.1.1.1's Purge Cache tool allows you to refresh 1.1.1.1's DNS cache for domain names. To refresh the cache for a domain name, visit the [Purge Cache page](https://one.one.one.one/purge-cache/).
 
 
-## What is query name minimization?
+## What is query name minimization
 
-Cloudflare minimizes privacy leakage by only sending minimal query name to authoritative DNS servers. For example, if a client is looking for foo.bar.example.com, the only part of the query 1.1.1.1 discloses to .com is that we want to know who’s responsible for example.com and the zone internals stay hidden.
+Cloudflare minimizes privacy leakage by only sending minimal query name to authoritative DNS servers. For example, if a client is looking for foo.bar.example.com, the only part of the query 1.1.1.1 discloses to .com is that we want to know who's responsible for example.com and the zone internals stay hidden.
 
 
-## What are root hints?
+## What are root hints
 
 For decreased latency, reduced privacy leakage of queries and lower load on the DNS system, 1.1.1.1 upstreams to [locally hosted root zone files](https://blog.cloudflare.com/f-root/).
 
-## Can IPs used by 1.1.1.1 be allowlisted?
+## Can IPs used by 1.1.1.1 be allowlisted
 
 Authoritative DNS providers may want to allowlist IP's 1.1.1.1 uses to query upstream DNS providers. The comprehensive list of IP's to allowlist is available at [https://www.cloudflare.com/ips/](https://www.cloudflare.com/ips/).
 

@@ -42,7 +42,7 @@ slug: 1.1.1.1/infrastructure/extended-dns-error-codes
             <td>3</td>
             <td>Stale Answer</td>
             <td><code>EDE: 3 (Stale Answer)</code></td>
-            <td>This is a silent error. It notifies that the DNS resolver could only return stale data. If the issue persists reach out on the 1.1.1.1 <a href="https://community.cloudflare.com/c/reliability/dns-1111/47">community forum</a>.</td>
+            The error indicates that the DNS resolver could only return stale data. If the issue persists, reach out on the 1.1.1.1 <a href="https://community.cloudflare.com/c/reliability/dns-1111/47">community forum</a>.
         </tr>
         <tr>
             <td>6</td>

@@ -16,7 +16,7 @@ The 1.1.1.1 resolver was designed with a privacy-first approach. Refer to our [d
 
 ## Configuring 1.1.1.1
 
-There are multiple ways to use 1.1.1.1 as an operator:
+Multiple methods exist for using 1.1.1.1 as an operator:
 
 * Including a [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/) or [DNS over TLS](/1.1.1.1/encryption/dns-over-tls/) proxy on end-user routers or devices (best for privacy).
 * Pushing 1.1.1.1 to devices via DHCP/PPP within an operator network (recommended; most practical).

@@ -16,7 +16,7 @@ The Agents SDK exposes two main APIs:
 
 :::note
 
-Agents require [Cloudflare Durable Objects](/durable-objects/), see [Configuration](/agents/getting-started/testing-your-agent/#add-the-agent-configuration) to learn how to add the required bindings to your project. 
+Agents require [Cloudflare Durable Objects](/durable-objects/), see [Configuration](/agents/getting-started/testing-your-agent/#add-the-agent-configuration) to learn how to add the required bindings to your project.
 
 :::
 
@@ -47,7 +47,7 @@ Instances of an Agent are addressed by a unique identifier: that identifier (ID)
 
 Writing an Agent requires you to define a class that extends the `Agent` class from the Agents SDK package. An Agent encapsulates all of the logic for an Agent, including how clients can connect to it, how it stores state, the methods it exposes, and any error handling.
 
-You can also define your own methods on an Agent: it's technically valid to publish an Agent only has your own methods exposed, and create/get Agents directly from a Worker.
+You can also define your own methods on an Agent: it is technically valid to publish an Agent only has your own methods exposed, and create/get Agents directly from a Worker.
 
 Your own methods can access the Agent's environment variables and bindings on `this.env`, state on `this.setState`, and call other methods on the Agent via `this.yourMethodName`.
 

@@ -40,7 +40,7 @@ The Agents SDK support Server-Sent Events directly: you can use SSE to stream da
 
 When an Agent is deployed to Cloudflare Workers, there is no effective limit on the total time it takes to stream the response back: large AI model responses that take several minutes to reason and then respond will not be prematurely terminated.
 
-Note that this does not mean the client can't potentially disconnect during the streaming process: you can account for this by either [writing to the Agent's stateful storage](/agents/api-reference/store-and-sync-state/) and/or [using WebSockets](/agents/api-reference/websockets/). Because you can always [route to the same Agent](/agents/api-reference/calling-agents/), you do not need to use a centralized session store to pick back up where you left off when a client disconnects.
+Note that this does not mean the client cannot potentially disconnect during the streaming process: you can account for this by either [writing to the Agent's stateful storage](/agents/api-reference/store-and-sync-state/) and/or [using WebSockets](/agents/api-reference/websockets/). Because you can always [route to the same Agent](/agents/api-reference/calling-agents/), you do not need to use a centralized session store to pick back up where you left off when a client disconnects.
 
 The following example uses the AI SDK to generate text and stream it back to the client. It will automatically stream the response back to the client as the model generates it:
 

@@ -176,7 +176,7 @@ Common use cases:
 
 ### SQL API
 
-Every individual Agent instance has its own SQL (SQLite) database that runs _within the same context_ as the Agent itself. This means that inserting or querying data within your Agent is effectively zero-latency: the Agent doesn't have to round-trip across a continent or the world to access its own data.
+Every individual Agent instance has its own SQL (SQLite) database that runs _within the same context_ as the Agent itself. This means that inserting or querying data within your Agent is effectively zero-latency: the Agent does not have to round-trip across a continent or the world to access its own data.
 
 You can access the SQL API within any method on an Agent via `this.sql`. The SQL API accepts template literals, and
 
@@ -280,7 +280,7 @@ export class ReasoningAgent extends Agent<Env> {
 
 </TypeScriptExample>
 
-This works because each instance of an Agent has its _own_ database, the state stored in that database is private to that Agent: whether it's acting on behalf of a single user, a room or channel, or a deep research tool. By default, you don't have to manage contention or reach out over the network to a centralized database to retrieve and store state.
+This works because each instance of an Agent has its _own_ database, the state stored in that database is private to that Agent: whether it is acting on behalf of a single user, a room or channel, or a deep research tool. By default, you do not need to manage contention or reach out over the network to a centralized database to retrieve and store state.
 
 ### Next steps