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-02 UTC."],[[["This webpage provides access to documentation for various versions of `google::cloud::storage::MD5HashValue`, ranging from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The documentation covers the `MD5HashValue` struct, which can be utilized for data integrity verification by providing a pre-computed MD5 hash."],["The documentation includes details on the `MD5HashValue()` constructor and a `static name()` function, which returns a `char const *` type."],["The use of providing a pre-computed MD5 hash is to enhance end-to-end data integrity verification in specific scenarios."],["A research document can be referenced in relation to this data integrity verification, hosted at this link \u003chttps://sigops.org/s/conferences/hotos/2021/papers/hotos21-s01-hochschild.pdf\u003e."]]],[]]
