You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When custom metadata is added to a cloud object and you access it via an HTTP GET request, each key-value pair should be included in the response headers with the prefix x-goog-meta-<key>. These key-value pairs are missing from the response headers when the storage emulator is used.
For example, if I add this metadata to a cloud object:
{"some": "metadata"}
then there should be a header in the response that looks like this:
{"x-goog-meta-some": "metadata"}
Instead, the only headers included in the response are:
Custom metadata (key-value pairs) should appear in the headers as key-value pairs like:
x-goog-meta-<key>: <value>
System (please complete the following information)
OS version: MacOS Monterey 12.4
Python version: 3.9.13
gcp-storage-emulator version: 2022.06.11
Additional context
I came across this while creating signed URLs to cloud objects and attempting to get their metadata, but this problem occurs for all URLs to cloud objects.
The text was updated successfully, but these errors were encountered:
Describe the bug
When custom metadata is added to a cloud object and you access it via an HTTP GET request, each key-value pair should be included in the response headers with the prefix
x-goog-meta-<key>
. These key-value pairs are missing from the response headers when the storage emulator is used.For example, if I add this metadata to a cloud object:
then there should be a header in the response that looks like this:
Instead, the only headers included in the response are:
To Reproduce
With the emulator running, execute the following python script:
This will raise:
Expected behavior
Custom metadata (key-value pairs) should appear in the headers as key-value pairs like:
System (please complete the following information)
Additional context
I came across this while creating signed URLs to cloud objects and attempting to get their metadata, but this problem occurs for all URLs to cloud objects.
The text was updated successfully, but these errors were encountered: