Request PATH includes FQDN and Protocol?

[charz]

I tried to use go sdk to head an object to an s3 compatible APIs, but I noticed the HEAD request include the FQDN and protocol (by tcpdump). Is that normal?

sws-sdk-go

HEAD http://swift.chhsu.com/test/test.zip HTTP/1.1
Host: swift.chhsu.com
User-Agent: aws-sdk-go/1.5.5 (go1.7.3; darwin; amd64)
Authorization: AWS4-HMAC-SHA256 Credential=demo/20161116/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=8597a1900784b56b31e41f8af88b9ca848c53f3c4d7d929a80264af12e817f23
X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
X-Amz-Date: 20161116T100714Z

s3cmd

HEAD /test/test.zip HTTP/1.1
Host: swift.chhsu.com
Accept-Encoding: identity
Content-Length: 0
Authorization: AWS demo:zrUAEJ5wCKgh2EsjcsU7LS3Ij1c=
x-amz-date: Wed, 16 Nov 2016 10:29:51 +0000

[jasdel]

Hi @charz this is correct. This is a valid HTTP request, but some server applications do not correctly support the absolute URL in the request's header.

The http.Client may use the absolute URL in the request's initial header if the request was built where the URL.Opaque field is set. The SDK does this to ensure no unexpected escaping is performed by the Go http Client that would break the request signature.

[charz]

Hi @jasdel,

Thanks for explaining that! I'm a newbie in Go, how can I switch to the common form of Request-URI (disable absolute URI)? just leave URL.Opaque as empty?

[jasdel]

In Go 1.5+ there is the URL.RawPath which is a better version of URL.Opaque as its just the URI Path and does not include the hostname. Switching to using RawPath instead of Opaque should prevent the need for the http client from using absolute URL.

[charz]

Thx, it works.

[charz]

BTW, use newer version sdk will fix the problem (> 1.6.12).