[jira] [Commented] (JCLOUDS-595) Investigate removing default content type

["Andrew Gaul (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481907#comment-14481907 ] 

Andrew Gaul commented on JCLOUDS-595:
-------------------------------------

WIP branch which has some strange behavior in Atmos and GCS tests:

https://github.com/andrewgaul/jclouds/tree/no-default-content-type

> Investigate removing default content type
> -----------------------------------------
>
>                 Key: JCLOUDS-595
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-595
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>            Reporter: Andrew Gaul
>
> 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|http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1]:
> {quote}
> 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".
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)