Configure HTTP Header Injection for specific URL patterns
Explanation
This policy enables defining a list of rules to inject custom HTTP headers into web requests matching specific URL patterns. Headers set by this policy take precedence over those that initially were present in the request, as well as modifications attempted by users or extensions.
A common use case for this policy is to enforce tenant access controls by injecting custom headers (e.g., X-Tenant-ID).
The policy accepts a list of Rules. Each Rule contains:
* patterns: A list of URL patterns to match. See how to format a URL pattern ( https://support.google.com/chrome/a?p=url_blocklist_filter_format ).
* headers: A list of objects representing headers to inject, each containing:
* name: The name of the header to inject.
* value: The value of the header to inject.
If multiple rules match a request, headers from all matching rules will be applied. In case there're multiple headers with the same name, the one with the most specific URL pattern will be applied. If patterns are equally specific, the one that appears last in the list will be applied.
Header names must be compliant with RFC 2616 ( https://www.rfc-editor.org/rfc/rfc2616 ). Header values must not contain NUL, CR or LF symbols. Individual headers must not exceed 8KB in size. Invalid headers and URL patterns will be ignored.
This policy is limited to a total of 500 URL patterns across all rules. Each rule can contain at most 20 headers. Patterns and headers beyond these thresholds will be ignored.
Note: If a URL pattern matches unencrypted schemes (http://, ws://, or when the scheme is omitted), the configured headers might be transmitted in plain text over an unencrypted channel and may be exposed to network observers. To protect sensitive or identifying header values, restrict URL patterns to encrypted schemes (https:// or wss://).
See https://chromeenterprise.google/policies/?policy=HttpHeaderInjection for more information about schema and formatting.
Example value:
[
{
"patterns": [
"https://example.com",
"https://.example.org"
],
"headers": [
{
"name": "X-Tenant-ID",
"value": "123456"
},
{
"name": "X-Custom-Header",
"value": "CustomValue"
}
]
}
]
Registry
HKEY_LOCAL_MACHINE\Software\Policies\BraveSoftware\BraveHKEY_CURRENT_USER\Software\Policies\BraveSoftware\Brave- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Computer (HKLM)
Enable
# Enable: brave/HttpHeaderInjection
$k = 'HKLM:\Software\Policies\BraveSoftware\Brave'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Configure HTTP Header Injection for specific URL patterns
Set-ItemProperty -Path $k -Name 'HttpHeaderInjection' -Value '<value>' -Type StringDisable
# Disable: brave/HttpHeaderInjection
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": brave/HttpHeaderInjection
$k = 'HKLM:\Software\Policies\BraveSoftware\Brave'
Remove-ItemProperty -Path $k -Name 'HttpHeaderInjection' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Configure HTTP Header Injection for specific URL patternsHttpHeaderInjection | Text boxtext | HttpHeaderInjection | REG_SZ | Max length: 1000000 |
Application
Brave (Brave Software) — November 2026 templates
Official templates downloaded on November 12, 2026.