Brave Browser: 1.98.63 to 1.99.55

Setting the policy specifies for which origins to allow all the HTTP authentication schemes Brave supports regardless of the AuthSchemes policy. [added: Starting in Brave version 161, this policy applies only to destination server origins and does not apply to proxy server authentication challenges. To allow all HTTP authentication schemes for proxy servers, use the AllHttpAuthSchemesAllowedForProxies policy instead. Prior to version 161, proxy servers matching this policy are also allowed to use all HTTP authentication schemes unless AllHttpAuthSchemesAllowedForProxies is set. ]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 host component (e.g., '*:8000' matches all hosts on port 8000). To match all schemes or all ports, omit the 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: https://example.com example.com *:8000 *

This policy controls the availability of the XSLT feature (the XSLTProcessor Javascript API and the XSL processing instruction). If this policy is set to Enabled, XSLT will be available, regardless of the default state of the feature in the browser. If this policy is set to Disabled, XSLT will be unavailable, regardless of the default state of the feature in the browser. If this policy is left unset, XSLT availability will be determined by the browser's default settings and field trials. This policy is a temporary measure, and will be removed in [removed: M164.][added: M176.]