List of URL patterns for which Chrome DevTools are blocked

Brak oficjalnego tekstu w tym języku (wyświetlono oryginał angielski)

Identyfikator zasady
DeveloperToolsAvailabilityBlocklist
Zakres
Konfiguracja komputera, Konfiguracja użytkownika
Obsługiwane w systemach
Microsoft Windows 7 or later
Źródło
Google Chrome Policy Templates (wersja 156.0.8078.80)
Kategoria
Google › Google Chrome

Opis

This policy can be used to block Chrome DevTools on specific URLs. For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format.

Chrome DevTools availability is evaluated at the target level. URL patterns are matched against the URL of each target being inspected (such as the main frame of a page, an embedded subframe, an extension, or a web application). The resulting behavior depends on whether the DeveloperToolsAvailabilityAllowlist policy is also set.

If this policy is set and DeveloperToolsAvailabilityAllowlist is not, a target's URL matching a pattern on this blocklist will block Chrome DevTools for that target (for example, a subframe whose URL matches this blocklist cannot be inspected, but the main page remains inspectable if its URL is not blocklisted). If a target's URL does not match any pattern, the availability is determined by the DeveloperToolsAvailability policy.

If both this and the DeveloperToolsAvailabilityAllowlist policies are set, the allowlist takes precedence. If a target's URL matches a pattern on the allowlist, it will be allowed, even if it also matches a pattern in this blocklist. If a target's URL matches a pattern on this blocklist (but not the allowlist), it will be blocked. If a target's URL matches neither, the DeveloperToolsAvailability policy will be used as a fallback.

If this policy is not set, the availability of Chrome DevTools is determined by the DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailability policies.

This policy affects Chrome DevTools, direct Chrome DevTools Protocol (CDP) access (for instance, when launched with --remote-debugging-port or --remote-debugging-pipe), and Chrome DevTools Protocol (CDP) access via chrome.debugger APIs. Both this policy and the RemoteDebuggingAllowed policy apply: RemoteDebuggingAllowed controls whether remote debugging can start, while this policy restricts whether individual targets can be inspected even when remote debugging is running.

This policy is limited to 1,000 entries.

Example value:

https://example.com
example.com
https://ssl.server.com
hosting.com/bad_path
https://server:8080/path
.exact.hostname.com
*
file://*

Opcje

  • List of URL patterns for which Chrome DevTools are blocked

Rejestr

Inne zasady w tej samej kategorii

Zobacz wszystkie zasady w tej kategorii (235)