mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-26 14:15:49 +03:00
[PR #176] [MERGED] Fix capitalisation in md5Hash metadata #405
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#405
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/fsouza/fake-gcs-server/pull/176
Author: @gh2k
Created: 2/12/2020
Status: ✅ Merged
Merged: 2/12/2020
Merged by: @fsouza
Base:
master← Head:fix-md5hash-case📝 Commits (1)
28c1b83Fix capitalisation in md5Hash metadata📊 Changes
3 files changed (+3 additions, -3 deletions)
View changed files
📝
fakestorage/object.go(+1 -1)📝
fakestorage/object_test.go(+1 -1)📝
fakestorage/response.go(+1 -1)📄 Description
The
md5Hashmember of metadata objects is currently being returned incorrectly asmd5hash.This breaks things like md5 hash validation in the nodejs client. For example, this line in Google's client checks for the
md5Hashmember:github.com/googleapis/nodejs-storage@63deb51d17/src/file.ts (L1385)See also the documentation at https://cloud.google.com/storage/docs/json_api/v1/objects
This patch renames the variable when serialising.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.