Destroyed Using S3Proxy with Azure Blob Storage (markdown)

Using-S3Proxy-with-Azure-Blob-Storage.md

@@ -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 <containername> 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://<proxy>/`
-* List blobs in a container: `curl http://<proxy>/<containername>`
-* Add a new container: `curl -X PUT http://<proxy>/<newcontainername>`
-* Add a new blob to a container: `curl -X PUT -T <filename> http://<proxy>/<containername>/<newblobname>`
-
-Many thanks to Krishna Parvathaneni for helping figuring all this out.
-	
-