-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Set User Agent Header for S3 Requests #2136
Labels
Comments
cc: @Xuanwo in case this option needs to be exposed in opendal |
As mentioned in apache/opendal#4389 (comment), this should already be simple. Let me mark this as |
ajschmidt8
added a commit
to ajschmidt8/sccache
that referenced
this issue
Mar 25, 2024
Closes mozilla#2136. This PR configures the S3 backend to use a custom HTTP client which has a user agent header set. The user agent header enables `sccache` users to write AWS policies to accept or reject `sccache` requests to an S3 bucket based on their `sccache` version.
sylvestre
pushed a commit
that referenced
this issue
Mar 25, 2024
* Set User Agent Header for S3 Requests Closes #2136. This PR configures the S3 backend to use a custom HTTP client which has a user agent header set. The user agent header enables `sccache` users to write AWS policies to accept or reject `sccache` requests to an S3 bucket based on their `sccache` version.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Feature Request
As defined by MDN (src):
I'd like to request that
sccache
set a user-agent header for requests to AWS/S3. The user-agent header should include thesccache
version.Use Case
AWS supports writing IAM policies that block access to resources based on the user-agent header: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-useragent.
I'd like to write a policy that denies access to an S3 bucket for versions of
sccache
that are affected by #2038.The text was updated successfully, but these errors were encountered: