x-amz-request-charged:requester in response
I enabled the requester pays property for my bucket.
(cross-account access to objects enabled for this bucket!)
Then I was trying to copy file from my requester pays bucket to another bucket. But RequesterCharged property in CopyObjectResponse was always null. And I also used fiddler to find x-amz-request-charged, I couldn't find it.
Could you please tell me how I can check the requester pays is worked for my bucket?
x-amz-request-charged is only added to the response if the requester was actually charged. When you were checking with the SDK and Fiddler, were you using a different account or your own? If you are the bucket owner of the requester pays bucket and you made the copy object request, you shouldn't see the request charged header.
Since Fiddler showed that the service also wasn't returning the header, I'm going to close this soon unless you can verify that the issue is in the SDK. If you need more help with the service, please try the AWS Forums.
@klaytaybai , thanks for quick response.
I have 2 aws accounts .
First account has bucket with enabled Requester pays, enabled Cross account functionality and this bucket has file that I was trying to copy to second bucket. The second bucket is in second account.
I made Copy request to copy file from first bucket(on Requester pays , First account) to second bucket(Second account).
I excepted to get x-amz-request-charged:requester in response, because I set always RequesterPayer property in my requests.
@klaytaybai do you understand my case that I was trying to do?
Hi @andrei-zubkovich, thanks for reporting this. You're right. The CopyObject operation isn't returning the RequesterCharged property (GetObject is working). I'll work internally to get this resolved.
Hi @klaytaybai . Thanks for response I'll wait fix. Could you please give me ETA?
Could you please tell me another ways to check RequesterPays functionality is working correctly?
@klaytaybai , are there news?
Most helpful comment
Hi @andrei-zubkovich, thanks for reporting this. You're right. The CopyObject operation isn't returning the RequesterCharged property (GetObject is working). I'll work internally to get this resolved.