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."],[[["This webpage provides access to the `Crc32cChecksumValue` structure documentation across multiple versions, from 2.11.0 up to the latest release candidate 2.37.0-rc."],["The primary function of `Crc32cChecksumValue` is to provide a pre-computed CRC32C checksum, enhancing data integrity verification when a checksum is available from outside the Google Cloud Storage system."],["The page also includes a link to a paper discussing data integrity, and details about the `name()` function's return type and description."],["The `Crc32cChecksumValue` structure has a constructor with no parameters, `Crc32cChecksumValue()`."]]],[]]
