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-22 UTC."],[[["The latest version available is 2.37.0-rc, with links to documentation for each version down to 2.11.0, all pertaining to the `MD5HashValue` structure within the Google Cloud Storage C++ library."],["This page focuses on pre-computed MD5 hash values and their use in improving end-to-end data integrity verification within applications."],["The documentation for each version includes information about the `MD5HashValue` structure, along with details on a constructor and the static `name()` function, which returns the name of the structure."],["The content references an external paper that may provide more information on MD5 hash usage and its relationship with cloud storage and integrity checks."]]],[]]
