couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Lenz (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (COUCHDB-1) MIME types for attachments
Date Sun, 25 May 2008 23:25:55 GMT

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

Christopher Lenz resolved COUCHDB-1.
------------------------------------

    Resolution: Fixed

Attachments now have a "content-type" field that's used as the Content-Type when retrieved.
Not sure when it was added, but it's there.

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message