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-01 UTC."],[[["The latest version available is 2.37.0-rc, which can be accessed via the provided link."],["The page provides a list of previous versions, ranging from 2.11.0 up to 2.36.0, including some patch releases."],["The content relates to `Crc32cChecksumValue`, and provides the functionality for applications to supply a pre-computed CRC32C checksum value, which improves data integrity verification."],["The documentation includes details on the `name()` function, returning the name as `char const *`."]]],[]]
