set content type of the object gives 403 error

[shebin-nginx]

local headers = util.new_headers()
headers['Content-Type']= 'text/plain'
...
....
local ok, response = s3:put("key", "value", header)

[shebin-nginx]

SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided.

[jie123108]

I passed the test with your case. It works in both s3 and minio. Can you check, if there is something wrong with the s3 configuration?

[shebin-nginx]

i use eu-west-1 .. everything works fine without the headers parameter
local ok, response = s3:put("key", "value") -> 200 ok and value in bucket
but
local ok, response = s3:put("key", "value", header) ->403

local headers = util.new_headers()
headers['Content-Type']= 'text/plain'
headers['Content-Encoding'] = 'None'

local s3 = awss3:new(aws_id, aws_secret, aws_bucket, {timeout=1000*10, aws_region=aws_region})

local ok, response = s3:put("test/key1", "data1", headers)
local ok, response = s3:put("test/key2", "data2",headers)

status:403, body:
SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.*****AWS4-HMAC-SHA256

** im calling it from nginx timer

[jie123108]

I'm sorry, I wasn't able to reproduce the issue, I used a eu-west-1 bucket for the test, and again Added the "Content-Type" header to the put request in test-s3.lua: test_01put() . But both requests were successful. You can test this by replacing it with your corresponding configuration with the following command:

cd path/to/lua-resty-s3
S3_CONFIG="S3_ACCESS_ID:S3_ACCESS_SECERT_KEY:resty-s3-eu-west-1:eu-west-1" resty -I lib test/test-s3.lua

[shebin-nginx]

Ok ... I tried to run hardcording those values in Auth classs it works fine

But when i run from the ngx.timer.at(0, func) context (even non modified util.headers ) gives unauthorized. bit strange