Created attachment 1339390 [details] rgw logs with debug_rgw=20 Description of problem: radosgw refuses upload when Content-Type missing from POST policy Upstream tracker: http://tracker.ceph.com/issues/20201 Version-Release number of selected component (if applicable): jewel 10.2.7 How reproducible: In the customer environment always When doing an S3 upload, if Content-Type is missing from the policy part of the upload, then radosgw refuses the upload with a 403 error, "Policy missing condition: Content-Type". The same upload to AWS S3 is successful, despite the Content-Type not being present in the uploaded policy. radosgw should accept this, for better interoperability. Context: this was encountered when using Fine Uploader https://github.com/FineUploader/fine-uploader to get files into an S3 bucket. When a user tries to upload a file which the browser can't identify (because it has an unrecognized or missing filename extension) then the Content-Type is not added to the POST'ed policy.
Created attachment 1339391 [details] ut-and-paste from the browser dev tools, showing the request headers and payload.
Attachments: options-and-failing-post-20170531.txt is a radosgw debug = 20 log, showing the OPTIONS pre-flight call succeeding, and the POST failing at "env var missing in policy: Content-Type" s3-upload-policy-missing-content-type-20170531.txt is cut-and-paste from the browser dev tools, showing the request headers and payload. Where are you experiencing the behavior? What environment? We first encountered this on Ceph 10.2.3. Our Ceph is 10.2.7 (latest Ubuntu packaged version for Xenial).
Master branch PR - https://github.com/ceph/ceph/pull/18658
customer has confirmed this resolved their issue, and has also updated Upstream tracker stating this: http://tracker.ceph.com/issues/20201
This is not in v12.2.1 upstream so we need to track this for RHCEPH 3.0 now as well.
Would you please cherry-pick the change to ceph-3.0-rhel-patches (with the RHCEPH 3 clone ID number, "Resolves: rhbz#1530775") so customers do not experience a regression?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0340
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days