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 webpage provides a comprehensive list of documentation for various versions of `MD5HashValue`, ranging from the latest release candidate (2.37.0-rc) down to version 2.11.0."],["This resource details the `MD5HashValue` in each version, showing the continuity and history of the code."],["The documentation highlights the use of pre-computed MD5 hash values to enhance end-to-end data integrity verification, particularly in scenarios where the hash might be available through external sources."],["There are also links provided to related functions and further material, such as a link to a research paper on data integrity verification."]]],[]]
