Describe the bug
PutObjectRequests from a GraalVM native image always set the content-type to application/octet-stream unless explicitly defined. This behavior can be traced back to the pattern being updated to exclude class files in native images. The resource "mime.types" doesn't make it to the native image and the content-type falls back to application/octet-stream.
Regression Issue
Expected Behavior
When uploading to s3 with a GraalVM native image, the content-type should be correctly identified if not set manually.
Current Behavior
Any upload with no content type set explicitly gets content-type application/octet-stream through a GraalVM native image.
Reproduction Steps
Upload jpeg to s3 with GraalVM native image without explicitly setting content-type.
Possible Solution
Modify pattern to include mime.types resource file and other required resources.
Additional Information/Context
No response
AWS Java SDK version used
2.44.6
JDK version used
21.0.11
Operating System and version
amazon linux 2023
Describe the bug
PutObjectRequests from a GraalVM native image always set the content-type to application/octet-stream unless explicitly defined. This behavior can be traced back to the pattern being updated to exclude class files in native images. The resource "mime.types" doesn't make it to the native image and the content-type falls back to application/octet-stream.
Regression Issue
Expected Behavior
When uploading to s3 with a GraalVM native image, the content-type should be correctly identified if not set manually.
Current Behavior
Any upload with no content type set explicitly gets content-type application/octet-stream through a GraalVM native image.
Reproduction Steps
Upload jpeg to s3 with GraalVM native image without explicitly setting content-type.
Possible Solution
Modify pattern to include mime.types resource file and other required resources.
Additional Information/Context
No response
AWS Java SDK version used
2.44.6
JDK version used
21.0.11
Operating System and version
amazon linux 2023