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 links to documentation for `Crc32cChecksumValue` across multiple versions, ranging from 2.37.0-rc down to 2.11.0."],["The `Crc32cChecksumValue` feature allows users to provide a pre-computed CRC32C checksum, which improves data integrity verification when the checksum is available through out-of-band means."],["The page includes a \"See Also\" link to a research paper discussing data integrity."],["The document details a constructor `Crc32cChecksumValue()` and a function `static name()` that will return `char const*`."]]],[]]
