Dongie Agnir
Dongie Agnir
@bennyflint Yes, there's been a few PR's merged that hopefully address some of these issues: - #475 - #480 - #526
#584
Hi don't believe the CLI actually sets `binary/octet-stream`. You can verify this by issuing a command like `aws s3 cp MY_BINARY_FILE s3://MY_BUCKET --debug` and see that it does not send...
Oops sorry looks like I didn't read your question close enough! I'm not sure what the exact reason is for the discrepancy but I suspect it's because `application/octet-stream` is registered...
As far as breaking change, customers may be relying on the fact that the default MIME for objects uploaded using the Java SDK to be `application/octet-stream` rather than `binary/octet-stream`. Do...
Are you referring to > We can also look into adding a default object MIME if that would be easiest for you. ? I was imagining just a new option...
> Can we run benchmarks to see how much performance impact this change would cause? Did a test with the following code Test code ```java public static void main(String[] args)...
Closing this for now because of performance regression concerns.
AFAIK we have not been able to repro this yet. I will try to look into this this week.
Feedback from v1: https://github.com/aws/aws-sdk-java/issues/1528