HTTP 400 · Bad Request
MD5_CHECKSUM_INVALID
The MD5 checksums do not match.
HTTP 400
Other
When & why it happens
The supplied md5 checksum is malformed, points to nothing the server recognises, or fails a server-side validity check.
Handling in gogram
Surfaced as *gogram.ErrResponseCode. Match on the message:
if err, ok := err.(*gogram.ErrResponseCode); ok {
if err.Message == "MD5_CHECKSUM_INVALID" {
// handle this error
}
}
Related errors
ABOUT_TOO_LONGAbout string too long.ACTIVE_USER_REQUIREDThe method is only available to already activated users.ADDRESS_INVALIDThe specified geopoint address is invalid.ALBUM_PHOTOS_TOO_MANYYou have uploaded too many profile photos, delete some before retrying.ANONYMOUS_REACTIONS_DISABLEDSorry, anonymous administrators cannot leave reactions or participate in polls.ARTICLE_TITLE_EMPTYThe title of the article is empty.AUTOARCHIVE_NOT_AVAILABLEThe autoarchive setting is not available at this time; please check the client configuration.BANK_CARD_NUMBER_INVALIDThe specified card number is invalid.BANNED_RIGHTS_INVALIDYou provided some invalid flags in the banned rights.BASE_PORT_LOC_INVALIDBase port location invalid.BOOSTS_EMPTYNo boost slots were specified.BOOSTS_REQUIREDThe specified channel must first be boosted by its users in order to perform this action.