Project

General

Profile

Actions
Copy link

Bug #6088

closed

rgw: When uploading via POST specifying text instead of file formdata input field, a subsequent GET fails with 500 error

Added by Brian Andrus over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
High
Assignee:
Yehuda Sadeh
Target version:
-
% Done:

0%

Source:
Support
Tags:
Backport:
dumpling, cuttlefish, bobtail
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Specific text from customer:

When uploading via POST if user specifies the "file" formdata input field as "text" instead of "file," RGW responds with a 200-range code, but upon a subsequent GET request to list objects in the bucket, RGW responds with a 500. After about 24 hours the problem goes away and the bucket can be listed again with no sign of the attempted erroneous upload.

Provided steps to reproduce:

  1. generate the signed S3 policy document and signature using the script in internal support ticket #466.
  2. Install Google Chrome Extension POSTMAN
  3. list an existing bucket with GET
  4. upload to the bucket using "file" as a text input field (replace your bucket name, "AWSAccessKeyId" value with your bucket's S3 Access Key, "policy" and "signature" values with the values generated in step #1)
  5. attempt to list the bucket again (repeat step #3), observe HTTP 500 error
Actions
Copy link

Also available in: Atom PDF