Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Fri, 7 Feb 2014 23:53:20 +0000 (UTC)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12693986.1391803877127.8980.1391817200924@arcas>
In-Reply-To: <JIRA.12693986.1391803877127@arcas>
References: <JIRA.12693986.1391803877127@arcas>
Subject: [jira] [Resolved] (COUCHDB-2054) Content-Encoding on requests is
 ignored; should decode or return 415
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/COUCHDB-2054?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Newson resolved COUCHDB-2054.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7.0

> Content-Encoding on requests is ignored; should decode or return 415
> --------------------------------------------------------------------
>
>                 Key: COUCHDB-2054
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2054
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues)=20
>          Components: HTTP Interface
>            Reporter: Jens Alfke
>             Fix For: 1.7.0
>
>
> CouchDB (as of 1.4) seems to ignore the "Content-Encoding" header on requ=
ests, and just parses the request body with no decoding. This causes incorr=
ect behavior =E2=80=94 most often it tries to parse the encoded data as JSO=
N and will fail and return 400.
> CouchDB should either decode the request body (e.g. unzip it), or else re=
turn a 415 status. Decoding would be quite useful: requests with large JSON=
 bodies (like revs_diff or the POST form of all_docs) can have their size c=
ut in half by gzip encoding.
> HTTP 1.1 spec for Content-Encoding:
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.11


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)