The field name should be e.g. image_type or image_mime_type, referring to the image's MIME type, rather than image_content_type, since only MIME-like messages have content types.
"Content-Type" comes from the HTTP response (and multipart request header) header of that name. There are many headers prefixed with Content- though, including Content-Length and Content-Encoding, and their purpose is to describe the content of the HTTP response. As an example of their meaning: the Content in this response has a Type of application/html, a Length of 12943 in bytes, and an Encoding of gzip.
The following are standard headers in HTTP request messages, HTTP response messages, or multipart/form-data messages:
Content-DispositionContent-EncodingContent-LanguageContent-LengthContent-LocationContent-MD5Content-RangeContent-Transfer-EncodingContent-Type
They describe the Content part of the message, just like the field image_type should describe the image part of the model object.
The field name should be e.g.
image_typeorimage_mime_type, referring to the image's MIME type, rather thanimage_content_type, since only MIME-like messages have content types."Content-Type" comes from the HTTP response (and multipart request header) header of that name. There are many headers prefixed with
Content-though, includingContent-LengthandContent-Encoding, and their purpose is to describe the content of the HTTP response. As an example of their meaning: theContentin this response has aTypeofapplication/html, aLengthof12943in bytes, and anEncodingofgzip.The following are standard headers in HTTP request messages, HTTP response messages, or
multipart/form-datamessages:Content-DispositionContent-EncodingContent-LanguageContent-LengthContent-LocationContent-MD5Content-RangeContent-Transfer-EncodingContent-TypeThey describe the
Contentpart of the message, just like the fieldimage_typeshould describe theimagepart of the model object.