Skip to content

[Rules] Add section on non-ASCII header values #17605

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 17, 2024
Merged

[Rules] Add section on non-ASCII header values #17605

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4d89279
[Rules] Add section on non-ASCII header values
pedrosousa Oct 17, 2024
1261042
Update example
pedrosousa Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/content/docs/rules/transform/managed-transforms/reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,12 @@ Adds HTTP headers with location information for the visitor's IP address to the
Turning on [IP geolocation](/network/ip-geolocation/) will send a `cf-ipcountry` HTTP header to your origin server even when **Add visitor location headers** is turned off.
:::

#### Encoding of non-ASCII header values

Cloudflare always converts non-ASCII characters to UTF-8 (using hexadecimal character representation) in HTTP request and response header values. This applies to location headers added by the **Add visitor location headers** managed transform.

For example, the header value `São Paulo` would be encoded as `S\u00c3\u00a3o Paulo`.

### Add "True-Client-IP" header

:::note
Expand Down
Loading