Brave Browser 1.91.168

Setting the policy specifies for which origins to allow all the HTTP authentication schemes Brave supports regardless of the AuthSchemes policy. Format the origin pattern according to this format (https://support.google.com/chrome/a?p=url_blocklist_filter_format). Up to 1,000 exceptions can be defined in AllHttpAuthSchemesAllowedForOrigins. Wildcards are allowed for the [removed: whole origin][added: host component (e.g., '*:8000' matches all hosts on port 8000). To match all schemes] or [removed: parts of][added: all ports, omit] the [removed: origin, either the scheme, host, port.][added: component entirely (e.g., 'example.com' matches any scheme and any port). A hostname (e.g., 'example.com') also matches its subdomains. To match a host exactly and exclude its subdomains, prepend it with a dot (e.g., '.example.com'). To match all origins, use a single asterisk ('*').] Example value: [removed: *.example.com][added: https://example.com example.com *:8000 *]

Configure how Brave downloads the foundational GenAI model and uses for inference locally. When the policy is set to Allowed (0) or not set, the model is downloaded automatically, and used for inference. When the policy is set to Disabled (1), the model will not be downloaded, and the existing model (if already downloaded) will be deleted. On desktop platforms, model downloading can also be disabled by [removed: ComponentUpdatesEnabled.][added: setting ComponentUpdatesEnabled to false.]

Setting the policy specifies the maximal number of simultaneous connections per proxy server for non-WebSocket requests. To modify WebSocket request limits, see MaxConnectionsPerProxyForWebSocket. Leaving the policy unset means a default of [removed: 32][added: 128] is used. Some web apps are known to consume many connections with hanging GETs, so setting a value below [removed: 32][added: 128] may lead to browser networking hangs if there are too many web apps with hanging connections open. Some proxy servers can't handle a high number of concurrent connections per client, which is solved by setting this policy to a lower value. The value should be equal to or higher than 6. Setting a value below that limit will cause 6 to be used. Lower below the default [removed: (32)][added: (128)] at your own risk. The value should be equal to or lower than 256 (99 in Brave 147 and earlier). Setting a value above that limit will cause 256 (99 in Brave 147 and earlier) to be used. Raise above the default [removed: (32)][added: (128)] at your own risk.

Setting the policy specifies the maximal number of simultaneous connections per proxy server for WebSocket requests. To modify non-WebSocket request limits, see MaxConnectionsPerProxy. Leaving the policy unset means a default of [removed: 32][added: 128] is used. Some web apps are known to consume many connections with hanging GETs, so setting a value below [removed: 32][added: 128] may lead to browser networking hangs if there are too many web apps with hanging connections open. Some proxy servers can't handle a high number of concurrent connections per client, which is solved by setting this policy to a lower value. The value should be equal to or higher than 6. Setting a value below that limit will cause 6 to be used. Lower below the default [removed: (32)][added: (128)] at your own risk. The value should be equal to or lower than 256. Setting a value above that limit will cause 256 to be used. Raise above the default [removed: (32)][added: (128)] at your own risk.

When this policy is Enabled, anonymous reporting of usage and crash-related data about Brave to Google is recommended to be enabled by default. Users will still be able to change this setting. When this policy is Disabled, anonymous reporting is disabled and no usage or crash data is sent to Google. Users won't be able to change this setting. When this policy is not set, users can choose the anonymous reporting behavior at installation or first run, and can change this setting later. (For Google Chrome OS, see DeviceMetricsReportingEnabled.) [removed: On Microsoft® Windows®, this policy ][added: If the RestructureMetricsConsentSettings experiment ]is [removed: only available ][added: active ]on [removed: instances that are joined to a Microsoft® Active Directory® domain, joined to Microsoft® Azure® Active Directory® or enrolled in Chrome Enterprise Core. On macOS, ][added: the device and both ]this policy [removed: is only available on instances that ][added: and the MetricsReportingLevel policy ]are [removed: managed via MDM, joined to a domain via MCX or enrolled in Chrome Enterprise Core.][added: set, the MetricsReportingLevel policy takes precedence.]

When this policy is Enabled, anonymous reporting of usage and crash-related data about Brave to Google is recommended to be enabled by default. Users will still be able to change this setting. When this policy is Disabled, anonymous reporting is disabled and no usage or crash data is sent to Google. Users won't be able to change this setting. When this policy is not set, users can choose the anonymous reporting behavior at installation or first run, and can change this setting later. (For Google Chrome OS, see DeviceMetricsReportingEnabled.) [removed: On Microsoft® Windows®, this policy ][added: If the RestructureMetricsConsentSettings experiment ]is [removed: only available ][added: active ]on [removed: instances that are joined to a Microsoft® Active Directory® domain, joined to Microsoft® Azure® Active Directory® or enrolled in Chrome Enterprise Core. On macOS, ][added: the device and both ]this policy [removed: is only available on instances that ][added: and the MetricsReportingLevel policy ]are [removed: managed via MDM, joined to a domain via MCX or enrolled in Chrome Enterprise Core.][added: set, the MetricsReportingLevel policy takes precedence.]