Project

General

Profile

Actions

Bug #270

closed

Content-Type not returned / saved correctly

Added by Wido den Hollander almost 14 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

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

Description

When setting the contentType when uploading, the gateway does not return this correctly.

Putting a file:

wido@wido-laptop:~$ s3 -u put blog/tesla_model_s.jpg filename=Ubuntu\ One/Documenten/Tesla/naias-2010-model-s-01.jpg contentType=image/jpeg
134710 bytes remaining (10% complete) ...
118326 bytes remaining (21% complete) ...
101942 bytes remaining (32% complete) ...
85558 bytes remaining (43% complete) ...
69174 bytes remaining (54% complete) ...
52790 bytes remaining (65% complete) ...
36406 bytes remaining (75% complete) ...
20022 bytes remaining (86% complete) ...
3638 bytes remaining (97% complete) ...
wido@wido-laptop:~$

With wireshark i verified if the client is setting the right contentType, it is (see attachment).

Then when GET'ing the file, the content-type text/plain is returned.

Going through "rgw_rest.cc" there seems to be support for Content-Type.


Files

Screenshot-bond0.pcap_-_Wireshark.png (135 KB) Screenshot-bond0.pcap_-_Wireshark.png Wido den Hollander, 07/11/2010 04:07 AM
return_content_length_header.patch (649 Bytes) return_content_length_header.patch Fix for returning the Content-Length Wido den Hollander, 07/14/2010 05:59 AM
Actions

Also available in: Atom PDF