couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Bisbee (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (COUCHDB-1) MIME types for attachments
Date Tue, 21 Feb 2012 21:32:48 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Bisbee closed COUCHDB-1.
----------------------------


Been resolved for a long time and CouchDB handles Content-Type for attachments just fine.
Closing.
                
> MIME types for attachments
> --------------------------
>
>                 Key: COUCHDB-1
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Noah Slater
>            Priority: Minor
>
> There is AFAICT currently no standard way to associate a MIME type with
> attachments. This is needed for CouchDB to be able to serve the attachment
> with the correct Content-Type header.
> There's already a type field in the attachment JSON structure, which I'd
> suggest should be renamed to encoding, as it's intended to determine how
> the content has been encoded in the JSON data (for example "base64"). With
> that out of the way, the type field should contain the MIME type. When an
> attachment is added, the client should be able to specify the MIME type
> using this field, but CouchDB could use a sane default
> ("application/octet-stream") if the field is missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message