Recorded when cache entry was found and produced a classification. Recorded when cache entry was not found. Recorded when cache entry was found but did not produce a classification, because it was outdated.

Application protocol used for HTTP response as defined in net::HttpConnectionInfo.

Error codes defined at https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#error-code

Should not happen. Stopped caching to read the response body of an auth response. A network error happened in the headers phase. A partial response could not be validated, and it was not due to auth. We have a full entry, but the server sent a range response that should replace it. Partial requests are hard to log. Original request had a Range header. The cache entry was truncated. Validating a partial entry, and they are hard to log. The request was externally conditionalized and didn't match our existing cache entry. Attempt to validate a partial response failed. Range-related failure led to calling IgnoreRangeRequest(). Cached IP address space blocked by Private Network Access policy. The reason is unknown. Querying HTTPS is disabled. Built-in DNS resolver is disabled. No DnsClient. DnsTask wasn't scheduled because it hadn't been working for a while. Insecure DnsTask was not allowed to query HTTPS. DnsTask was executed but fell back to the system task.

Tracks the result of querying for an INTEGRITY or HTTPSSVC record. This enum can represent each of Chrome's supported RCODE values as well as any unrecognized RCODE values. It also has the TimedOut value to represent queries that timed out. IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml

The case where it returns false. No enabled client hints were provided. The origin of the request does not match the main frame origin. The optimization for subframes is disabled. One or more hints in the Accept-CH frame are not in the enabled hints list. An error page was shown. This bucket encompasses all others and works as a total count for error pages (instead of the histogram's total sample count which doesn't reflect that information). An error page was shown with at least a "Reload" button on it. An error page was shown with at least a "Reload" button on it and the user pressed that button. An error page was previously loaded with a "Reload" button and another load error happened as a result of the user pressing that button. An error page was shown with at least a "Show Saved Copy" button on it. An error page was shown with at least a "Show Saved Copy" button on it and the user pressed that button. An error page was previously loaded with a "Show Saved Copy" button and another load error happened as a result of the user pressing that button. An error page was shown with at least a "More" (aka "Details") button on it and the user pressed that button. An error page was previously loaded and the user started a reload by pressing the browser's reload button. An error page was shown with at least a "Reload" and a "Show Saved Copy" buttons on it. Note that this is not exclusive with the respective individual button buckets. An error page was shown with at least a "Reload" and a "Show Saved Copy" buttons on it and the user pressed the "Reload" button. Note that this is not exclusive with the respective individual button buckets. An error page was shown with at least a "Reload" and a "Show Saved Copy" buttons on it and the user pressed the "Show Saved Copy" button. Note that this is not exclusive with the respective individual button buckets. An error page was shown with the offline dino image and and the user activated it (to play the dino game). An error page was shown with at least a "Show Cached Copy" button on it. An error page was shown with at least a "Show Cached Copy" button on it and the user pressed that button. Obsolete. Obsolete. An error page was shown with at least a "Diagnose Error" button on it and the user pressed that button. Obsolete. Obsolete. Obsolete. Obsolete. An error page was shown with at least a "Download Page Later" button on it. An error page was shown with at least a "Download Page Later" button on it and the user pressed that button. A list containing at least one item of offline content suggestions was shown in the expanded/shown state. An item from the offline content suggestions list was clicked. A link that opens the downloads page was clicked. A summary of available offline content was shown. A list containing at least one item of offline content suggestions was shown in the collapsed/hidden state. The error page was shown because the device is offline (dino page). An error page was shown with at least a "Sign in to network" button on it and the user pressed that button. Persisted cache was successfully loaded. snapshot.baf file was not large enough to contain a magic number. No data restored. snapshot.baf file couldn't be loaded into memory. No data restored. snapshot.baf had an incorrect or old magic number. No data restored. Deserialization of snapshot.baf contents failed. No data restored. journal.baj file couldn't be loaded into memory. Journal not restored. journal.baj file was older than snapshot.baf. Journal not restored. journal.baj file was not large enough to contain a magic number. Journal not restored. journal.baj file had an incorrect or old magic number. Journal not restored. Deserialization of journal.baj contents failed. Journal not restored. Deserialization of a journal entry failed. Journal loading incomplete. Couldn't write a new snapshot.baf file. Persistence abandoned. Couldn't create a new journal.baj file. Persistence abandoned. Couldn't write to journal.baj file. Persistence abandoned. Target directory doesn't exist, and can't create it. Persistence abandoned. Directory already existed. Directory successfully created. Directory didn't exist and couldn't be created. The No-Vary-Search header was successfully parsed. The No-Vary-Search header was not present in the response headers. The No-Vary-Search header value was equivalent to the default (vary on all query parameters), and so was ignored. The value of the No-Vary-Search header could not be parsed as a structured headers dictionary. The "key-order" parameter does not have a boolean value. The "params" parameter is not an inner list, or contains a non-string value. The "except" parameter is not an inner list, or contains a non-string value. The "except" parameter was supplied, but the "params" parameter did not have a boolean true value. The file was not present in the old location. The file was present in both the old and the new locations. The file in the old location was deleted. The file was present in both the old and the new locations. An attempt to delete the file in the old location failed. The file was moved from the old location to the new location. An attempt to move the file from the old location to the new location failed. The request was not suitable, or the feature was disabled. There was no match in the No-Vary-Search cache. There was a match, but the URL was identical so it has no effect. There was a match, and the original cache entry was used. There was a match, but it was unusable due to in-memory hints, so the match was not used. There was a match, but the corresponding disk cache entry was missing or could not be loaded, so the match was not used. There was a match, but the disk cache entry needed revalidation in read-only mode, so the match was not used. There was a match, but the disk cache entry has an incomplete body. Partial responses are not supported for No-Vary-Search, so the match was not used. There was a match, but revalidation was required and the request could not be conditionalized, so the match was not used. There was a match, and the original cache entry was successfully revalidated. There was a match, and the original cache entry was updated. There was a match, but the cache lock timed out. The request then bypassed the cache, so the match was not used.

The result of a TLS connection that offered ECH

Whether a TLS connection relied on the trust anchor ID retry.

Handshake not completed via Upgrade over HTTP/1 connection. Server responded to Upgrade request with invalid status. Server responded to Upgrade request with empty response. Server responded to Upgrade request with 101 status but there was some other network error. Server responded to Upgrade request with invalid Upgrade header. Server responded to Upgrade request with invalid Sec-WebSocket-Accept header. Server responded to Upgrade request with invalid Connection header. Server responded to Upgrade request with invalid Sec-WebSocket-Protocol header. Server responded to Upgrade request with invalid Sec-WebSocket-Extensions header. Upgrade request failed due to other network error. Connected via Upgrade over HTTP/1 connection. Handshake not completed over an HTTP/2 connection. Server responded to WebSocket request over an HTTP/2 connection with invalid status code. Server responded to WebSocket request over an HTTP/2 connection with invalid sec-websocket-protocol header. Server responded to WebSocket request over an HTTP/2 connection with invalid sec-websocket-extensions header. WebSocket request over an HTTP/2 connection failed with some other error. Connected over an HTTP/2 connection. Handshake not completed over an HTTP/3 connection. Server responded to WebSocket request over an HTTP/3 connection with invalid status code. Server responded to WebSocket request over an HTTP/3 connection with invalid sec-websocket-protocol header. Server responded to WebSocket request over an HTTP/3 connection with invalid sec-websocket-extensions header. WebSocket request over an HTTP/3 connection failed with some other error. Connected over an HTTP/3 connection. Bad UID. Bad hash. Bad key. Bad length. Bad data. Invalid signature. Bad version of provider. Invalid algorithm specified. Invalid flags specified. Invalid type specified. Key not valid for use in specified state. Hash not valid for use in specified state. Key does not exist. Insufficient memory available for the operation. Object already exists. Access denied. Object was not found. Data already encrypted. Invalid provider specified. Invalid provider type specified. Provider's public key is invalid. Key set does not exist. Provider type not defined. The provider type, as registered, is invalid. The key set is not defined. The key set, as registered, is invalid. Provider type does not match registered value. The digital signature file is corrupt. Provider DLL failed to initialize correctly. Provider DLL could not be found. The keyset parameter is invalid. An internal error occurred. A base error occurred. Provider could not perform the action because the context was acquired as silent. The security token does not have storage space available for an additional container. The profile for the user is a temporary profile. The key parameters could not be set because the configuration service provider (CSP) uses fixed parameters. The supplied handle is invalid. The parameter is incorrect. The buffer supplied to a function was too small. The requested operation is not supported. No more data is available. The supplied buffers overlap incorrectly. The specified data could not be decrypted. An internal consistency check failed. This operation requires input from the user. The cryptographic provider does not support Hash Message Authentication Code (HMAC). The device that is required by this cryptographic provider is not ready for use. The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider. The validation of the provided data failed the integrity or signature validation. Incorrect password. Encryption failed. This is an error mask to convert TPM hardware errors to win errors. Authentication failed. The index to a PCR, DIR or other register is incorrect. One or more parameter is bad. An operation completed successfully but the auditing of that operation failed. The clear disable flag is set and all clear operations now require physical access. Activate the Trusted Platform Module (TPM). Enable the Trusted Platform Module (TPM). The target command has been disabled. The operation failed. The ordinal was unknown or inconsistent. The ability to install an owner is disabled. The key handle cannot be interpreted. The key handle points to an invalid key. Unacceptable encryption scheme. Migration authorization failed. PCR information could not be interpreted. No room to load key. There is no Storage Root Key (SRK) set. An encrypted blob is invalid or was not created by this TPM. The Trusted Platform Module (TPM) already has an owner. The TPM has insufficient internal resources to perform the requested action. A random string was too short. The TPM does not have the space to perform the operation. The named PCR value does not match the current PCR value. The paramSize argument to the command has the incorrect value . There is no existing SHA-1 thread. The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, you might need to replace your TPM hardware or motherboard. The authorization for the second key in a 2 key function failed authorization. The tag value sent to for a command is invalid. An IO error occurred transmitting information to the TPM. The encryption process had a problem. The decryption process did not complete. An invalid handle was used. The TPM does not have an Endorsement Key (EK) installed. The usage of a key is not allowed. The submitted entity type is not allowed. The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. Signed data cannot include additional DER information. The key properties in TPM_KEY_PARMs are not supported by this TPM. The migration properties of this key are incorrect. The signature or encryption scheme for this key is incorrect or not permitted in this situation. The size of the data (or blob) parameter is bad or inconsistent with the referenced key. A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob. Either the physicalPresence or physicalPresenceLock bits have the wrong value. The TPM cannot perform this version of the capability. The TPM does not allow for wrapped transport sessions. TPM audit construction failed and the underlying command was returning a failure code also. TPM audit construction failed and the underlying command was returning success. Attempt to reset a PCR register that does not have the resettable attribute. Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. Make identity blob not properly typed. When saving context identified resource type does not match actual resource. The TPM is attempting to execute a command only available when in FIPS mode. The command is attempting to use an invalid family ID. The permission to manipulate the NV storage is not available. The operation requires a signed command. Wrong operation to load an NV key. NV_LoadKey blob requires both owner and blob authorization. The NV area is locked and not writtable. The locality is incorrect for the attempted operation. The NV area is read only and can't be written to. There is no protection on the write to the NV area. The family count value does not match. The NV area has already been written to. The NV area attributes conflict. The structure tag and version are invalid or inconsistent. The key is under control of the TPM Owner and can only be evicted by the TPM Owner. The counter handle is incorrect. The write is not a complete write of the area. The gap between saved context counts is too large. The maximum number of NV writes without an owner has been exceeded. No operator AuthData value is set. The resource pointed to by context is not loaded. The delegate administration is locked. Attempt to manage a family other than the delegated family. Delegation table management not enabled. There was a command executed outside of an exclusive transport session. Attempt to context save a owner evict controlled key. The DAA command has no resources availble to execute the command. The consistency check on DAA parameter inputData0 has failed. The consistency check on DAA parameter inputData1 has failed. The consistency check on DAA_issuerSettings has failed. The consistency check on DAA_tpmSpecific has failed. The atomic process indicated by the submitted DAA command is not the expected process. The issuer's validity check has detected an inconsistency. The consistency check on w has failed. The handle is incorrect. Delegation is not correct. The context blob is invalid. Too many contexts held by the TPM. Migration authority signature validation failure. Migration destination not authenticated. Migration source incorrect. Incorrect migration authority. Attempt to revoke the EK and the EK is not revocable. Bad signature of CMK ticket. There is no room in the context list for additional contexts. TPM 2.0: Inconsistent attributes. TPM 2.0: Hash algorithm not supported or not appropriate. TPM 2.0: Value is out of range or is not correct for the context. TPM 2.0: Hierarchy is not enabled or is not correct for the use. TPM 2.0: Key size is not supported. TPM 2.0: Mask generation function not supported. TPM 2.0: Mode of operation not supported. TPM 2.0: The type of the value is not appropriate for the use. TPM 2.0: The Handle is not correct for the use. TPM 2.0: Unsupported key derivation function or function not appropriate for use. TPM 2.0: Value was out of allowed range. TPM 2.0: The authorization HMAC check failed and DA counter incremented. TPM 2.0: Invalid nonce size. TPM 2.0: Unsupported or incompatible scheme. TPM 2.0: Structure is wrong size.. TPM 2.0: Unsupported symmetric algorithm or key size, or not appropriate for instance. TPM 2.0: Incorrect structure tag. TPM 2.0: Union selector is incorrect. TPM 2.0: The TPM was unable to unmarshal a value because there were not enough octets in the input buffer. TPM 2.0: The signature is not valid. TPM 2.0: Key fields are not compatible with the selected use. TPM 2.0: A policy check failed. TPM 2.0: Integrity check failed. TPM 2.0: Invalid ticket. TPM 2.0: Reserved bits not set to zero as required. TPM 2.0: Authorization failure without DA implications. TPM 2.0: The policy has expired. TPM 2.0: The command code in the policy is not the command code of the command or the command code in a policy command references a command that is not implemented. TPM 2.0: Public and sensitive portions of an object are not cryptographically bound. TPM 2.0: Curve not supported. TPM 2.0: Point is not on the required curve. TPM 2.0: TPM not initialized. TPM 2.0: Commands not being accepted because of a TPM failure. TPM 2.0: Improper use of a sequence handle. TPM 2.0: TPM_RC_PRIVATE error. TPM 2.0: TPM_RC_HMAC. TPM 2.0: TPM_RC_DISABLED. TPM 2.0: Command failed because audit sequence required exclusivity. TPM 2.0: Unsupported ECC curve. TPM 2.0: Authorization handle is not correct for command. TPM 2.0: Command requires an authorization session for handle and is not present. TPM 2.0: Policy failure in Math Operation or an invalid authPolicy value. TPM 2.0: PCR check fail. TPM 2.0: PCR have changed since checked. TPM 2.0: The TPM is not in the right mode for upgrade. TPM 2.0: Context ID counter is at maximum. TPM 2.0: authValue or authPolicy is not available for selected entity. TPM 2.0: A _TPM_Init and Startup(CLEAR) is required before the TPM can resume operation. TPM 2.0: The protection algorithms (hash and symmetric) are not reasonably balanced. The digest size of the hash must be larger than the key size of the symmetric algorithm. TPM 2.0: The TPM command's commandSize value is inconsistent with contents of the command buffer; either the size is not the same as the bytes loaded by the hardware interface layer or the value is not large enough to hold a command header. TPM 2.0: Command code not supported. TPM 2.0: The value of authorizationSize is out of range or the number of octets in the authorization Area is greater than required. TPM 2.0: Use of an authorization session with a context command or another command that cannot have an authorization session. TPM 2.0: NV offset+size is out of range. TPM 2.0: Requested allocation size is larger than allowed. TPM 2.0: NV access locked. TPM 2.0: NV access authorization fails in command actions TPM 2.0: An NV index is used before being initialized or the state saved by TPM2_Shutdown(STATE) could not be restored. TPM 2.0: Insufficient space for NV allocation. TPM 2.0: NV index or persistent object already defined. TPM 2.0: Context in TPM2_ContextLoad() is not valid. TPM 2.0: chHash value already set or not correct for use. TPM 2.0: Handle for parent is not a valid parent. TPM 2.0: Some function needs testing. TPM 2.0: returned when an internal function cannot process a request due to an unspecified problem. This code is usually related to invalid parameters that are not properly filtered by the input unmarshaling code. TPM 2.0: The sensitive area did not unmarshal correctly after decryption - this code is used in lieu of the other unmarshaling errors so that an attacker cannot determine where the unmarshaling error occurred. The command was blocked. The specified handle was not found. The TPM returned a duplicate handle and the command needs to be resubmitted. The command within the transport was blocked. The command within the transport is not supported. The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. SelfTestFull has not been run. The TPM is currently executing a full selftest. The TPM is defending against dictionary attacks and is in a time-out period. TPM 2.0: Gap for context ID is too large. TPM 2.0: Out of memory for object contexts. TPM 2.0: Out of memory for session contexts. TPM 2.0: Out of shared object/session memory or need space for internal operations. TPM 2.0: Out of session handles - a session must be flushed before a new session may be created. TPM 2.0: Out of object handles - the handle space for objects is depleted and a reboot is required. TPM 2.0: Bad locality. TPM 2.0: The TPM has suspended operation on the command; forward progress was made and the command may be retried. TPM 2.0: The command was canceled. TPM 2.0: TPM is performing self-tests. TPM 2.0: The TPM is rate-limiting accesses to prevent wearout of NV. TPM 2.0: Authorization for objects subject to DA protection are not allowed at this time because the TPM is in DA lockout mode. TPM 2.0: The TPM was not able to start the command. TPM 2.0: the command may require writing of NV and NV is not current accessible.. An internal error has occurred within the Trusted Platform Module support program. One or more input parameters is bad. A specified output pointer is bad. The specified context handle does not refer to a valid context. A specified output buffer is too small. An error occurred while communicating with the TPM. One or more context parameters is invalid. The TBS service is not running and could not be started. A new context could not be created because there are too many open contexts. A new virtual resource could not be created because there are too many open virtual resources. The TBS service has been started but is not yet running. The physical presence interface is not supported. The command was canceled. The input or output buffer is too large. A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer. The TBS service has been disabled. No TCG event log is available. The caller does not have the appropriate rights to perform the requested operation. The TPM provisioning action is not allowed by the specified flags... The Physical Presence Interface of this firmware does not support the requested method. The requested TPM OwnerAuth value was not found. The TPM provisioning did not complete. An unexpected internal error has occurred in the Platform Crypto Provider.