Swift check content_type header exists before using

Solution Unverified - Updated -

Issue

  • This KCS is to document a Red Hat backport from upstream tracker.

  • When downloading an object, the content_type header is inspected to determine if a directory needs to be created. This header is assumed to always be in the response; if it isn't an Exception is raised. swiftclient should not assume content_type will always be set.

Environment

  • Red Hat Enterprise Linux OpenStack Platform 5 on RHEL 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In