Skip to content

Add non-configurable headers guidance to custom user agent section #28953

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
kathayl merged 1 commit into from
Mar 13, 2026
+1 −1
Merged

Add non-configurable headers guidance to custom user agent section #28953

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion src/content/partials/browser-rendering/setting-custom-user-agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,5 @@
You can change the user agent at the page level by passing `userAgent` as a top-level parameter in the JSON body. This is useful if the target website serves different content based on the user agent.

:::note
The `userAgent` parameter does not bypass bot protection. Requests from Browser Rendering will always be identified as a bot.
The `userAgent` parameter does not bypass bot protection. Requests from Browser Rendering will always be identified as a bot. Because the User-Agent is configurable, destination servers looking to identify or block Browser Rendering requests should use the [non-configurable headers](/browser-rendering/reference/automatic-request-headers/#non-configurable-headers) rather than relying on the User-Agent string.
:::
Loading