-
If you create a client without specifying the signature version in the config it will not honor the range set in the get _object.
boto3 1.13.2
python 3.8
Steps to reproduce
#create client w…
-
## Summary
I believe this is a regression after #8403 @borisno2
After adding `"use client"` to [packages/fields-document/src/validation.ts](packages/fields-document/src/validation.ts), things bre…
-
### Checkboxes for prior research
- [X] I've gone through [Developer Guide](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide) and [API reference](https://docs.aws.amazon.com/AWSJav…
-
Brackets 1.2
Kubuntu 14.04
the new versions 2.x are not working on linux, the error given is "Max connection attempts reached"
I just did a very simple demo file, demo.scss
```
$demo:1px;
.demo{wid…
-
### Confirmation
- [X] My issue isn't already found on the issue tracker.
- [X] I have replicated my issue using the latest version of the provider and it is still present.
### Terraform and Cl…
-
## Expected behavior
"api": "S3v2" in config should cause the mc client to use v2 signature. Moreover, there shouldn't be a difference in the http headers seen with the --debug flag, and in the heade…
-
### Describe the issue
@aws-sdk/signature-v4 has been moved to @smithy/signature-v4.
Cloudfront edge lambdas have native support for @aws-sdk but not for @smithy.
I am confused about what i should …
dza89 updated
5 months ago
-
### Describe the feature
Hi!
aws-sdk v2 had an option `signatureVersion: 'v2' | 'v4'` which allowed to switch to the old and deprecated AWS SigV2.
### Use Case
While it is recomended to use …
-
PR #1 includes unit tests that ought to run via CI. The boilerplate necessary to run tests via CI is in PR #2.
> PR #2 is cribbed from the [idc_migration](https://github.com/jhu-idc/idc_migration…
-
## NOTE
If this case is urgent, please subscribe to [Subnet](https://min.io/pricing) so that our 24/7 support team may help you faster.
## Expected Behavior
Ability to set auth to v2 via some…