-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Storage: 'Blob.reload' does not pass encryption headers #7440
Copy link
Copy link
Closed
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Per the docs on customer-supplied encryption keys, the
X-Goog-Encryption-Keyheader applies not only the the blob / object's payload, but also to its CRC32c checksum and MD5 hash fields.Blob.reload(inherited from_helpers._PropertyMixindoes not pass those headers, and thus the returned resource will not have thecrc32cormd5Hashfields set.