* 15 minitues timeskew
* Add x-amz-date header or query parameter check
* Change the timeskew logic to first get client req auth type
* When v2,x-amz-date header format is rfc2616,when v4,is iso8601
* If have both x-amz-date header and date header in v2 auth,date value in
stringtosign is x-amz-date header value,CanonicalizedAmzHeaders
have no x-amz-header.
Ref Delete example in site:
http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html
* Fix v2 query auth:
If expires is nil ,does not mean that the auth type is not query
auth type.
Ref http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html#RESTAuthenticationQueryStringAuth
It says that 'Additionally, you can limit a pre-signed request by specifying an expiration time.'
This approach requires three times as many operations as the optimal
approach. Implementing this correctly requires exposing the
underlying multipart operations in jclouds. Most s3-tests pass but
test_list_multipart_upload still fails:
References #2.