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-04-17 UTC."],[[["This webpage provides documentation for the `Crc32cChecksumValue` struct across multiple versions, ranging from 2.11.0 to the latest release candidate 2.37.0-rc."],["The latest version documented is the release candidate 2.37.0-rc, with previous versions available for reference down to version 2.11.0."],["The `Crc32cChecksumValue` allows for pre-computed CRC32C checksum values to be provided to the client library, which can enhance data integrity verification."],["The documentation includes a static `name()` function and a constructor, along with a link to an external resource regarding integrity in storage systems."]]],[]]
