PutObject with streaming results empty Content-Encoding

[trung]

Describe the bug

As described in aws/aws-sdk-java-v2#4642

When using default S3 Async Client, then the issue is no longer there.

Expected Behavior

No Content-Encoding metadata

Current Behavior

Content-Encoding has empty value

Reproduction Steps

// using CRT
S3AsyncClient s3AsyncClient = S3AsyncClient.crtBuilder()
        .region(awsRegion)
        .credentialsProvider(awsCredentialsProvider)
        .build();

// not using CRT
// S3AsyncClient.builder()
//        .region(awsRegion)
//        .credentialsProvider(awsCredentialsProvider)
//        .build();

Path f = Paths.get("test.pdf");
Flux<ByteBuffer> fileFlux = Flux.using(
    () -> new FileReader(f.toFile()),
    reader -> Flux.fromStream(new BufferedReader(reader).lines()).map(s -> ByteBuffer.wrap(s.getBytes(
        StandardCharsets.UTF_8))),
    reader -> {
      try {
        reader.close();
      } catch (IOException e) {
        throw new RuntimeException(e);
      }
    }
);

final CompletableFuture<PutObjectResponse> s3Future =
        s3AsyncClient.putObject(
            PutObjectRequest.builder()
                .bucket("mybucket")
                .key("test.pdf")
                .contentLength(Files.size(f))
                .contentType(MediaType.APPLICATION_PDF_VALUE)
                .build(),
            AsyncRequestBody.fromPublisher(fileFlux));

test.pdf has Content-Encoding with empty value.

While if using non CRT S3 Async Client, test.pdf won't have Content-Encoding

Possible Solution

No response

Additional Information/Context

aws/aws-sdk-java-v2#4642

aws-crt-java version used

0.28.10

Java version used

17

Operating System and version

MacOS 14.1.1 (23B81)

[jmklix]

Do you have the logs that show the request for both with and without the CRT?

[jmklix]

Can you update to the latest version of the Java sdk? It looks like this was fixed in aws-crt-java version 0.28.11 and the Java sdk updated it's crt version to that this past week

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.