From 29c4bf59d4798f08a93ee329eaf23cb465ca1516 Mon Sep 17 00:00:00 2001 From: Andrew Gaul Date: Thu, 6 Oct 2016 21:25:38 -0700 Subject: [PATCH] Destroyed Using S3Proxy with Azure Blob Storage (markdown) --- Using-S3Proxy-with-Azure-Blob-Storage.md | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 Using-S3Proxy-with-Azure-Blob-Storage.md diff --git a/Using-S3Proxy-with-Azure-Blob-Storage.md b/Using-S3Proxy-with-Azure-Blob-Storage.md deleted file mode 100644 index 5df7837..0000000 --- a/Using-S3Proxy-with-Azure-Blob-Storage.md +++ /dev/null @@ -1,22 +0,0 @@ -#A few things to keep in mind - -* Set `S3PROXY_AUTHORIZATION=none`. With the default of `S3PROXY_AUTHORIZATION=aws-v2` you get this error on PUT requests: AWS authentication requires a valid Date or x-amz-date header -* Start the container with `-e LOG_LEVEL=trace` for troubleshooting issues -* The clock inside a docker container can drift pretty badly on a dev laptop. If the time discrepancy gets [more than 15 minutes](https://msdn.microsoft.com/en-us/library/azure/dd179428.aspx#Anchor_0) then authentication will fail with 403 Server failed. In the trace output you'll find messages saying: - -_403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature_ - -and - -_Request date header too old_. You can easily verify the time in a container running `docker exec -it date` and compare to your dev laptops time. **Restarting docker** on windows resets the clock. - -#Examples for Basic operations - -* List containers in a storage account: `curl http:///` -* List blobs in a container: `curl http:///` -* Add a new container: `curl -X PUT http:///` -* Add a new blob to a container: `curl -X PUT -T http:////` - -Many thanks to Krishna Parvathaneni for helping figuring all this out. - -