The application may be able to obtain a CRC32C checksum in some out-of-band way. For example, if the object was downloaded from some other cloud storage service, or because the application already queried the GCS object metadata. In these cases, providing the value to the client library improves the end-to-end data integrity verification.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The latest version available is 2.37.0-rc, which can be accessed via the provided link."],["The provided content lists multiple versions of `Crc32cChecksumValue`, starting from the latest release candidate (2.37.0-rc) and going down to version 2.11.0."],["The page documents `Crc32cChecksumValue`, with a focus on using the checksum in out-of-band situations to improve end-to-end data integrity verification."],["The `name()` function for `Crc32cChecksumValue` is documented, with a return type of `char const *`, but without a specified description."],["There is a link provided to a paper detailing integrity checks in distributed storage systems, which may serve as further reading."]]],[]]
