Files
versitygw/s3api
mu-adnan 6121d52778 fix: apply default Content-Type in POSTObject
Browser-based POST uploads (POST /{bucket}) read Content-Type straight out
of the form fields, so a form without a content-type field stored the object
with an empty Content-Type. On read, fasthttp substitutes its own default,
so the object came back as "text/plain; charset=utf-8" rather than just
missing a type.

Fall back to defaultContentType ("binary/octet-stream") when the form field
is absent or empty, matching PutObject, CopyObject and CreateMultipartUpload,
as well as AWS S3 and Ceph RGW.
2026-08-29 00:38:34 +05:00
..
2026-06-15 14:48:31 +04:00
2026-06-15 14:48:31 +04:00
2026-06-15 14:48:31 +04:00