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

ASF GitHub Bot commented on COUCHDB-2562:
-----------------------------------------

Github user kxepal commented on the pull request:

    https://github.com/apache/couchdb-couch/pull/40#issuecomment-77608180
  
    +1 in general.
    Btw, in light of 
[COUCHDB-2562](https://issues.apache.org/jira/browse/COUCHDB-2562) how do you 
feel is "stream" feed type is good one or there could be something better?


> 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)

Reply via email to