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-02 UTC."],[[["The latest version available is 2.37.0-rc, which can be accessed via a specific link."],["The provided content lists multiple versions of `Crc32cChecksumValue`, starting from 2.11.0 up to the latest release candidate 2.37.0-rc, with links to the documentation for each version."],["This page focuses on a pre-computed CRC32C checksum value and how providing it to the client library enhances end-to-end data integrity verification."],["The `Crc32cChecksumValue` function `name()` returns the type `char const *`, and there is a link provided to a paper that discusses this function in detail."]]],[]]
