SignV2 Query-string authentication?

[nathany]

When uploading a file to S3 using PutReaderWithHeaders.

Query-string authentication requires the Signature, Expires and AWSAccessKeyId parameters

I'm curious why SignV2 chooses to use query-string authentication?

req.URL.RawQuery = queryVals.Encode()

vs. setting a header:

req.Header.Set("Authorization", "AWS "+ auth.AccessKey +":"+ string(signature))

[nathany]

Though this is probably not the reason why I'm getting this authentication error. Still digging.

[nathany]

Hm. I'm not really sure why SignV2 isn't working for me. 😦

This is using:

"gopkg.in/amz.v3/aws"
"gopkg.in/amz.v3/s3"

[nathany]

It could just be a bad error message. This issue may be to do with uploading files containing spaces.

The documentation says to use the "un-decoded" path, which I originally thought was decoded like URL.Path, but it looks like it actually means encoded, as with URL.RequestURI() with less the RawQuery part.

http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html

https://github.com/go-amz/amz/blob/v3/aws/sign.go#L54