Kami edited a comment on issue #1530: URL: https://github.com/apache/libcloud/issues/1530#issuecomment-748482513
I also verified we correctly pass headers as provided by the user directly to the API endpoint. Per S3 API docs, it's indeed limitation of the S3 API - https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html: > ... User-defined metadata is a set of key-value pairs. Amazon S3 stores user-defined metadata keys in lowercase. ... And here are a couple of more links for reference:: * https://stackoverflow.com/questions/59627280/setting-custom-metadata-to-an-object-in-google-cloud-storage * https://stackoverflow.com/questions/56852315/gcp-https-load-balancers-will-convert-http-1-1-header-names-to-lowercase-coul * https://groups.google.com/forum/#!msg/google-appengine/rS_2v6bTaVo/pCRQcYE7DAAJ In short, since metadata in our implementation is sent as part of the HTTP request headers, using only lower case value is safer in any case. And as said above - it appears to work via the console since that likely utilizes native Google Storage JSON API and not the S3 compatible XML one. So maybe for now we just document this as a limitation in our Google Storage driver docs? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
