@dkocher commented

Depending on the API requirement in S3, URIs are escaped. What is the issue?

Vito Ordaz commented

I just asking, because in S3 there is no requirement for escaping path for canonical string (http://docs.amazonwebservices.com/AmazonS3/latest/dev/RESTAuthentication.html). But other clients (for example s3curl) don't escape object path. That is why I have problem with swift3 (middleware for Swift to emulate S3 API), path in request URL and path used for cannonocal string are not equal, then request can't be authorized, because canonical string generated by swift3 use path, that in request.

@dkocher commented

The documentation quoted says Append the path part of the un-decoded HTTP Request-URI, up-to but not including the query string. We depend on Jets3t doing the work here for us.