-
Notifications
You must be signed in to change notification settings - Fork 9.9k
Update automatic-request-headers.mdx #26365
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.
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
base: production
Are you sure you want to change the base?
Conversation
update -web bot auth links -how to make WAF skip rule
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
update faq to point to allowlist instructions
| The `Signature` headers use an authentication method called [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/). Web Bot Auth leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. To verify a request originated from Cloudflare Browser Rendering, use the keys found on [this directory](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev/.well-known/http-message-signatures-directory) to verify the `Signature` and `Signature-Input` found in the headers from the incoming request. A successful verification proves that the request originated from Cloudflare Browser Rendering and has not been tampered with in transit. | ||
|
|
||
| ### Allowlist Browser Rendering with Web Bot Auth | ||
| If you need Browser Rendering to access resources on **your own zone** that’s protected by Cloudflare's Bot Protection, create a [WAF skip rule](/waf/custom-rules/skip/) that matches the **Web Bot Auth** `Signature-agent` to the **domain only**: `web-bot-auth.cloudflare-browser-rendering-085.workers.dev`, and require the presence of `Signature` and `Signature-Input`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's not clear enough. The value of the Signature-Agent header is "https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev" with quotes included. So either we use this value here, or clarify that header must include web-bot-auth.cloudflare-browser-rendering-085.workers.dev
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

update
-web bot auth links
-how to make WAF skip rule
Summary
Screenshots (optional)
Documentation checklist