Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for requester pays requests #100

Closed
mitar opened this issue Apr 11, 2013 · 8 comments
Closed

Support for requester pays requests #100

mitar opened this issue Apr 11, 2013 · 8 comments
Labels
feature-request A feature should be added or improved.

Comments

@mitar
Copy link

mitar commented Apr 11, 2013

It seem there is no support for Requester Pays Buckets.

@lsegal
Copy link
Contributor

lsegal commented Apr 11, 2013

There should be support for this feature in S3.putBucketRequestPayment. Is this what you are looking for, or is it not working for you?

@mitar
Copy link
Author

mitar commented Apr 11, 2013

No. Requester Pays buckets are buckets where a person who does getObject pays for it.

mitar added a commit to peerlibrary/aws-sdk-js that referenced this issue Apr 11, 2013
@mitar
Copy link
Author

mitar commented Apr 11, 2013

I made a simple patch which makes it work for me.

@lsegal
Copy link
Contributor

lsegal commented Apr 11, 2013

You are correct that getObject has no parameter to specify the 'x-amz-request-payer' header. That's something that can be easily added (I was writing this as you just did). In the meantime, you can also workaround this by adding the header to the request yourself:

var req = s3.getObject(params);
req.httpRequest.headers['x-amz-request-payer'] = 'requester';
req.on('complete', function (resp) { console.log(resp.data) });
req.send();

@mitar
Copy link
Author

mitar commented Apr 11, 2013

Aha, good, a workaround. :-) Thanks.

@mitar
Copy link
Author

mitar commented Jun 27, 2013

This was not yet fixed?

@AdityaManohar
Copy link
Contributor

@mitar Requester pays buckets are now supported in the SDK. Thanks for reporting!

@lock
Copy link

lock bot commented Sep 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

3 participants