diff --git a/alb/request-handling.mdx b/alb/request-handling.mdx index e80a627..e23f7e5 100644 --- a/alb/request-handling.mdx +++ b/alb/request-handling.mdx @@ -8,7 +8,7 @@ Datum's Application Load Balancer (ALB) runs on Datum's edge, the proxies that s | Question | Short answer | |---|---| -| Where is the client's IP address? | The last entry of `X-Forwarded-For`, and `X-Envoy-External-Address`. See [Find the client's IP address](#find-the-clients-ip-address). | +| Where is the client's IP address? | The last entry of `X-Forwarded-For`, and `X-Envoy-External-Address`. See [Find the client's IP address](#find-the-client’s-ip-address). | | How long can a response stay open? | About 15 seconds by default, streaming included. You can raise it to 1 hour. See [How long a response can stay open](#how-long-a-response-can-stay-open). | | Is plain HTTP redirected to HTTPS? | Only when Force HTTPS or a redirect rule is on. See [Plain HTTP](#plain-http). | @@ -39,7 +39,7 @@ Origin sees: X-Forwarded-For: 198.51.100.23,203.0.113.7 | Header | What the origin sees | |---|---| -| `X-Forwarded-For` | The client's IP address, appended. See [Find the client's IP address](#find-the-clients-ip-address). | +| `X-Forwarded-For` | The client's IP address, appended. See [Find the client's IP address](#find-the-client’s-ip-address). | | `X-Envoy-External-Address` | The client's IP address. Replaces any value the client sent. | | `X-Forwarded-Proto` | `https` or `http`: the protocol the client used to reach the edge. Replaces any value the client sent. Measured on `networkService` backends. | | `X-Request-Id` | A unique ID that the edge generates for each request. | diff --git a/domain-dns/private-dns-zones.mdx b/domain-dns/private-dns-zones.mdx index a39b36d..b797831 100644 --- a/domain-dns/private-dns-zones.mdx +++ b/domain-dns/private-dns-zones.mdx @@ -60,7 +60,7 @@ spec: `db.datum.internal` now resolves on that network only. You can't add records at or below `instances.datum.internal`, which Compute owns. -You can also use the `datumctl dns` plugin, which needs DNS enabled in the project. See [Troubleshooting](/domain-dns/troubleshooting#dns-isnt-enabled-for-my-project). Every network has its own `datum.internal` zone. If your project has more than one network, add `--vpc` with the network's name to say which zone you mean: +You can also use the `datumctl dns` plugin, which needs DNS enabled in the project. See [Troubleshooting](/domain-dns/troubleshooting#dns-isn’t-enabled-for-my-project). Every network has its own `datum.internal` zone. If your project has more than one network, add `--vpc` with the network's name to say which zone you mean: ```bash datumctl dns record create datum.internal db AAAA fd20:1::20 --vpc default diff --git a/guides/alb-as-httpd.mdx b/guides/alb-as-httpd.mdx index 34257ab..e21d0c6 100644 --- a/guides/alb-as-httpd.mdx +++ b/guides/alb-as-httpd.mdx @@ -486,7 +486,7 @@ An app that worked behind its old proxy can still fail behind the ALB, because s - **Uploads**: the WAF rejects large request bodies, even in Observe mode. See [WAF](https://github.com/datum-labs/shorts/blob/main/gists/alb/alb-as-httpd-reference.md#waf) in the reference and [WAF configuration](/alb/configuration/waf). - **WebSockets**: supported to Compute workloads, and not ended by the response timeout. See [WebSockets](/alb/request-handling#websockets). - **Rate limits**: counted per edge node, not across the whole ALB. See [Rate limits](https://github.com/datum-labs/shorts/blob/main/gists/alb/alb-as-httpd-reference.md#rate-limits). -- **Client IP**: your app reads it from forwarded headers. See [Find the client's IP address](/alb/request-handling#find-the-clients-ip-address). +- **Client IP**: your app reads it from forwarded headers. See [Find the client's IP address](/alb/request-handling#find-the-client’s-ip-address). ### Response timeout diff --git a/locations.mdx b/locations.mdx index ee37287..41ad288 100644 --- a/locations.mdx +++ b/locations.mdx @@ -17,7 +17,7 @@ Datum takes the opposite approach: every Region and Availability Zone correspond - **Data location** — because each Region maps to a specific country, you can reason about which jurisdiction your workloads run in. Regulatory and export-control requirements can still limit where a workload may run, and they take precedence over the placement rules below. - **Real choice and control** — you pick where things run based on your own requirements (proximity to users, legal residency, avoiding a single point of failure), the same way you would if you were choosing between physical data centers, rather than accepting one big undifferentiated "everywhere." -Most customers pick a Region close to their users or their required jurisdiction. To add redundancy, or to serve users in more than one part of the world, deploy to more than one Region. To see which Regions your project can use today, see [Check what's available to your project](#check-whats-available-to-your-project). +Most customers pick a Region close to their users or their required jurisdiction. To add redundancy, or to serve users in more than one part of the world, deploy to more than one Region. To see which Regions your project can use today, see [Check what's available to your project](#check-what’s-available-to-your-project). ## Naming convention