Repository navigation
Document Forwarded header support in web-bot-auth - #772
Merged
Merged
Conversation
Add a transitive trust section covering the Forwarded header: how it reaches the origin on signed requests, what the signature covers, and how to set it from automation code.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
ulziibay-kernel
marked this pull request as ready for review
November 19, 2026 22:25
hiroTamada
approved these changes
Nov 19, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a "Transitive trust with the Forwarded header" section to the Web Bot Auth page, matching the egress-proxy change in kernel/kernel#5629: on WBA-signed requests Kernel now forwards a client-supplied
Forwardedheader to the origin, and with Kernel's WBA token the header is part of the signature's covered components.The section shows what the header is, what the signature covers in each key path (Kernel's token vs. own keys), and how to set it from automation code with CDP extra headers in TypeScript and Python. It also states that unsigned egress keeps stripping the header.
Preview: https://tbd-6fc993ce-hypeship-wba-forwarded-docs.mintlify.app/browsers/bot-detection/web-bot-auth
Note
Low Risk
Documentation-only update with no runtime or security logic changes.
Overview
Adds a Transitive trust with the Forwarded header section to the Web Bot Auth docs, aligned with Kernel egress behavior: on WBA-signed traffic, a client-set RFC 7239
Forwardedheader (e.g. operator identity) is passed through to the origin instead of stripped.The new text distinguishes KERNEL's WBA token (header in signature covered components) vs your own keys (must add
forwardedto covered components), and includes TypeScript and Python examples using Playwright/CDPsetExtraHTTPHeaders. It also notes that unsigned requests still stripForwardedlike other proxy-revealing headers.Reviewed by Cursor Bugbot for commit 365bd42. Bugbot is set up for automated code reviews on this repo. Configure here.