-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload not possible #731
Comments
It appears that the S3 client added metadata with characters that Azure does not support. Consider remapping them via https://github.com/gaul/s3proxy/wiki/Middleware-user-metadata-replacer. |
Thank you for your reply. |
Can you check which characters your client is sending? You can do this by running S3Proxy with more logging:
|
I set it to trace but I'm to blind to se the corret line. Can you find the character?
|
I disabled SSL and used WireShark to capture the upload. I have also used another commercial product. It works with the same client application. I hope you can help! |
Hi,
I'm using the s3proxy in Azure. It runs in a container instance. The instance listens on port 8080 and 443.
The certificate is created by the startup script using the commands you provided in your wiki.
The storage is an Azure StorageAccount (BlobStorage).
I'm using curl and S3Browser (https://s3browser.com/) to test the proxy.
I have enabled the proxy's debug mode. From the many lines it generates, I found that this might be the error:
[s3proxy] W 11-25 14:11:47.970 S3Proxy-Jetty-20 o.g.s.o.e.j.server.HttpChannel:793 |::] handleException /test2/local-identity.txt java.io.IOException: com.azure.storage.blob.models.BlobStorageException: Status Code 400, "<?xml version="1.0" encoding="utf-8"?><Error><Code>InvalidMetadata</Code><Message>The metadata provided is invalid. It contains characters that are not allowed.
My Configuration:
S3PROXY_AUTHORIZATION=none
S3PROXY_CORS_ALLOW_ALL=false
S3PROXY_CORS_ALLOW_CREDENTIAL=
S3PROXY_CORS_ALLOW_HEADERS=
S3PROXY_CORS_ALLOW_METHODS=
S3PROXY_CORS_ALLOW_ORIGINS=
S3PROXY_CREDENTIAL=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX X
S3PROXY_ENCRYPTED_BLOBSTORE=
S3PROXY_ENCRYPTED_BLOBSTORE_PASSWORD=
S3PROXY_ENCRYPTED_BLOBSTORE_SALT=
S3PROXY_ENDPOINT=http://0.0.0.0:8080
S3PROXY_IDENTITY=06291a9a-XXXX-XXXX-XXXX-140160e6a711
S3PROXY_IGNORE_UNKNOWN_HEADERS=false
S3PROXY_KEYSTORE_P ASSWORD=XXXXXXXXXX
S3PROXY_KEYSTORE_PATH=/opt/s3proxy/keystore.p12
S3PROXY_READ_ONLY_BLOBSTORE=false
S3PROXY_VIRTUALHOST=
JCLOUDS_AZUREBLOB_AUTH=azureKey
JCLOUDS_CREDENTIAL=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
JCLOUDS_ENDPOINT=https://XXXXXXXXX XXX.blob.core.windows.net/
JCLOUDS_FILESYSTEM_BASEDIR=/data
JCLOUDS_IDENTITY=XXXXXXXXXX
JCLOUDS_KEYSTONE_PROJECT_DOMAIN_NAME=
JCLOUDS_KEYSTONE_SCOPE=
JCLOUDS_KEYSTONE_VERSION=
JCLOUDS_PROVIDER=azureblob-sdk
JCLOUDS_REGION=
JCLOUDS_REGIONS=us-east-1
Thanks for any help
Robert
The text was updated successfully, but these errors were encountered: