couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kaj Nielsen (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (COUCHDB-2258) CouchDB 1.6.0 returns wrong Content-Type
Date Tue, 24 Jun 2014 23:45:25 GMT

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

Kaj Nielsen reopened COUCHDB-2258:
----------------------------------

    Skill Level: New Contributors Level (Easy)

Logic fail.

"Always worked like this" does not equal "Working correctly".

The content returned is always JSON, so the MIME type returned should always be application/json.

That's what the RFC says, and that's what CouchDB should do (regardless of how it historically
has interpreted Accept */*).


> CouchDB 1.6.0 returns wrong Content-Type
> ----------------------------------------
>
>                 Key: COUCHDB-2258
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2258
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Kaj Nielsen
>
> CouchDB returns JSON documents.
> So the Content-Type set by CouchDB should be "application/json".
> Instead:
> > GET /db/doc HTTP/1.1
> > Host: localhost:5984
> >
> < HTTP/1.1 200 OK
> < Server: CouchDB/1.6.0 (Erlang OTP/R15B01)
> < ETag: "167-37f82fdbfdc49d38b1c66815deb1e338"
> < Date: Tue, 24 Jun 2014 22:26:39 GMT
> < Content-Type: text/plain; charset=utf-8
> < Content-Length: 649
> < Cache-Control: must-revalidate
> <
> ...
> As seen above, CouchDB returns text/plain.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message