[JCLOUDS-595] Investigate removing default content type

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jclouds-core
• Assignee: Unassigned
• Reporter: Andrew Gaul
• Created: 12/Jun/14 01:01
• Updated: 06/Apr/15 20:50

Description

Presently ContentMetadataBuilder.contentType defaults to "application/unknown". In many cases the application does not known the content type and might prefer to allow the object store to detect a more precise type which this default interferes with. From section 7.2.1 of RFC 2616:

Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. If the media type remains unknown, the recipient SHOULD treat it as type "application/octet-stream".