The application may be able to obtain a MD5 hash 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 is a release candidate version for the `MD5HashValue` structure."],["A comprehensive list of previous versions, ranging from 2.36.0 down to 2.11.0, is provided for the `MD5HashValue` structure in the storage reference."],["Providing a pre-computed MD5 hash value can improve end-to-end data integrity verification, especially in cases where the object's MD5 hash is already known."],["The document specifies that the `MD5HashValue` has a function called `name()` that returns a `char const *`."],["This documentation contains details about the `MD5HashValue` struct in the google cloud storage C++ library and links to a paper on data integrity."]]],[]]
