You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2015/01/30 20:55:34 UTC

[jira] [Commented] (COUCHDB-2562) Wrong Content-Type for continuous changes feed

    [ https://issues.apache.org/jira/browse/COUCHDB-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299147#comment-14299147 ] 

Alexander Shorin commented on COUCHDB-2562:
-------------------------------------------

A bit better reference: http://dataprotocols.org/ndjson/ || https://github.com/ndjson/ndjson-spec
Sounds good for me.

> Wrong Content-Type for continuous changes feed
> ----------------------------------------------
>
>                 Key: COUCHDB-2562
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2562
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Nathan Vander Wilt
>
> When a client requests a continuous changes feed and includes an "Accept: application/json" header, the response comes back as "Content-Type: application/json" even though the content is not parseable as JSON.
> I think the proper thing to do in this specific case is to respond with "406 Not Acceptable", or if this is considered too extreme and HTTP allows it, proceed anyway but claim "Content-Type: application/x-ldjson" instead (see http://en.wikipedia.org/wiki/Line_Delimited_JSON#MIME_Type_and_File_Extensions).
> This is an issue that some acknowledged as a bug during the discussion on https://issues.apache.org/jira/browse/COUCHDB-604 but didn't get its own ticket.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)