Bug #6088
closedrgw: When uploading via POST specifying text instead of file formdata input field, a subsequent GET fails with 500 error
0%
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:
- generate the signed S3 policy document and signature using the script in internal support ticket #466.
- Install Google Chrome Extension POSTMAN
- list an existing bucket with GET
- 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)
- attempt to list the bucket again (repeat step #3), observe HTTP 500 error
Updated by Ian Colle over 10 years ago
- Priority changed from Normal to High
- Source changed from other to Support
Updated by Yehuda Sadeh over 10 years ago
Bug confirmed on latest. From what I can tell cache entry for bucket gets corrupted.
Updated by Yehuda Sadeh over 10 years ago
- Status changed from New to Fix Under Review
- Backport set to dumpling, cuttlefish, bobtail
Updated by Yehuda Sadeh over 10 years ago
- Assignee changed from Yehuda Sadeh to Josh Durgin
Updated by Josh Durgin over 10 years ago
- Status changed from Fix Under Review to 4
- Assignee changed from Josh Durgin to Yehuda Sadeh
Looks good to me, is there an associated s3-tests branch as well?
Updated by Yehuda Sadeh over 10 years ago
The bug reproduction was manual, not sure how easy it'd be creating a boto based test for that.
Updated by Yehuda Sadeh over 10 years ago
- Status changed from 4 to Resolved
Fixed, commit:c8ec532fadc0df36e4b265fe20a2ff3e35319744. Also cherry-picked to bobtail, cuttlefish, and dumpling.