Skip to content

Conversation

@kathayl
Copy link
Contributor

@kathayl kathayl commented Nov 7, 2025

update
-web bot auth links
-how to make WAF skip rule

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

update 
-web bot auth links
-how to make WAF skip rule
@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2025

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/browser-rendering/ @mchenco, @cloudflare/pcx-technical-writing, @celso, @danielgek, @kathayl, @ToriLindsay

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`.
Copy link
Contributor

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

Copy link
Contributor Author

@kathayl kathayl Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated copy to include this highlighted part of your feedback. but not sure how to do the latter feedback

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants