libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Farrell (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LIBCLOUD-433) libcloud throws an exception when content-type is not supplied and it cannot guess the content type successfully
Date Wed, 06 Nov 2013 01:32:18 GMT
Michael Farrell created LIBCLOUD-433:
----------------------------------------

             Summary: libcloud throws an exception when content-type is not supplied and it
cannot guess the content type successfully
                 Key: LIBCLOUD-433
                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-433
             Project: Libcloud
          Issue Type: Bug
          Components: Storage
    Affects Versions: 0.13.2
            Reporter: Michael Farrell


Whenever uploading a file using libcloud, it will throw an exception if there is no content-type
specified and it cannot guess the content-type from the file extension.

Somewhere along the line of django-randomfilenamestorage, django-storages and libcloud (I
suspect in django-storages), the content-type of the file will be stripped if the browser
passes a content-type on an uploaded file of application/octet-stream.

When this lands in libcloud.storage.base.StorageDriver._upload_object, libcloud attempts to
guess the file's content-type from it's extension if none is supplied.  When this fails, an
AttributeError is raised.

Instead of throwing an exception, why not send the content-type of unknown bytestreams: application/octet-stream.

Patch is incoming.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message