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-03-21 UTC."],[[["The page provides a comprehensive list of available versions for the `MD5HashValue` structure, ranging from the latest release candidate (2.37.0-rc) down to version 2.11.0."],["Each version listed links to its specific documentation for the `MD5HashValue` structure."],["The document explains the use of providing a pre-computed MD5 hash value to improve end-to-end data integrity verification."],["The document also references an external paper regarding data integrity and details the class Constructors and functions."],["The main function mentioned `static name()` returns the type of `char const *` but has no provided description."]]],[]]
