[LIBCLOUD-433] libcloud throws an exception when content-type is not supplied and it cannot guess the content type successfully

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.13.2
• Component/s: Storage
• Assignee: Unassigned
• Reporter: Michael Farrell
• Created: 06/Nov/13 01:31
• Updated: 09/Dec/13 14:33
• Resolved: 09/Dec/13 14:33

Description

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.