S3.head_object uses deprecated HEAD request form

[IanButterworth]

It was a bit of a pain to track this down because the depwarning doesn't give a correct location

┌ Warning: Using "HEAD" in AWS requests to return headers is deprecated, use `@service S3 use_response_type=true` to return an `AWS.Response` allowing for header access via `response.headers`.
│   caller = ip:0x0
└ @ Core :-1

But it turns out that S3.head_object uses a deprecated request form

AWS.jl/src/services/s3.jl

Line 3120 in de0d4c3

"HEAD", "/$(Bucket)/$(Key)"; aws_config=aws_config, feature_set=SERVICE_FEATURE_SET

So the user can hit this without doing anything wrong AFAICT

[mattBrzezinski]

That's a fun one, looks like there are three instances of using HTTP HEAD requests,

• AWS.jl/src/services/s3.jl

  Line 3025 in de0d4c3

  return s3("HEAD", "/$(Bucket)"; aws_config=aws_config, feature_set=SERVICE_FEATURE_SET)

• AWS.jl/src/services/s3.jl

  Line 3120 in de0d4c3

  "HEAD", "/$(Bucket)/$(Key)"; aws_config=aws_config, feature_set=SERVICE_FEATURE_SET

• AWS.jl/src/services/mediastore_data.jl

  Line 44 in de0d4c3

  "HEAD", "/$(Path)"; aws_config=aws_config, feature_set=SERVICE_FEATURE_SET

[IanButterworth]

Is there a simple fix here? I'd love to not see the warning

[mattBrzezinski]

The issue stems from here, I think @omus this can be removed? As we do another check in each of the XML, JSON, MIME if statements for returning back headers?

Longer-term wrapping up the remaining tasks for AWS@2, removing the deprecations fixes this problem.

[IanButterworth]

friendly bump

[mattBrzezinski]

I'm away on holidays for the remainder of the year essentially, this is quite a low priority issue and a proper fix is quite far away.

One suggestion if this is getting very annoying is to use Suppressor.jl which would work around this temporarily.

[IanButterworth]

Just a friendly check in on this. I see this warning in so many logs, and I don't like relying on Suppressor etc.

[mattBrzezinski]

Sorry Ian, I've really been too busy to spend any time on this package and realistically probably won't have the capacity any time in the near future. :(

[IanButterworth]

No worries! I'll see if I can figure it out