en-US chrome computer user

List of proxy servers allowing all HTTP authentication schemes

Verified with Google Chrome — updated on November 3, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome\HTTP authentication

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~HTTPAuthentication/AllHttpAuthSchemesAllowedForProxies

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

macOS / Linux preference AllHttpAuthSchemesAllowedForProxies
Android restriction AllHttpAuthSchemesAllowedForProxies
Supported platforms
  • Google Chrome (Linux) — since version 156
  • Google Chrome (Mac) — since version 156
  • Google Chrome (Windows) — since version 156
  • Google Chrome (Android) — since version 156
  • Google ChromeOS (Google ChromeOS) — since version 156

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Options

List of proxy servers allowing all HTTP authentication schemes
List (registry values) list list under Software\Policies\Google\Chrome\AllHttpAuthSchemesAllowedForProxies

Description

Setting the policy specifies for which proxy servers to allow all the HTTP authentication schemes Google Chrome supports, regardless of the AuthSchemes policy. Format the proxy server pattern according to the URL blocklist filter format (https://support.google.com/chrome/a?p=url_blocklist_filter_format). Up to 1,000 exceptions can be defined. Wildcards are allowed for the host component (e.g., '*:8080' matches all proxies on port 8080). A hostname (e.g., 'proxy.example.com') also matches its subdomains. To match a host exactly and exclude its subdomains, prepend it with a dot (e.g., '.proxy.example.com'). If this policy is not set, only the HTTP authentication schemes specified in AuthSchemes (or the default schemes if unset) are supported for proxy authentication. Example value: https://proxy.example.com:8443 proxy.example.com:8080 *.corp.example.com:8080

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: List of proxy servers allowing all HTTP authentication schemes
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\AllHttpAuthSchemesAllowedForProxies]
; List values: enter one value per line in the builder UI.
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: List of proxy servers allowing all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\AllHttpAuthSchemesAllowedForProxies'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI.

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview