Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of jens@couchbase.com designates
 206.225.164.30 as permitted sender)
From: Jens Alfke <jens@couchbase.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Date: Mon, 6 Feb 2012 10:21:48 -0800
Subject: Multipart vs chunked
Thread-Topic: Multipart vs chunked
Thread-Index: Aczk/DEYM8vs+ApxSo6RoKc1pAePZQ==
Message-ID: <5E8EB1DF-FCD8-4EDC-AA67-88DF00FE26A1@couchbase.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

tl;dr: CouchDB* doesn=92t seem to correctly parse MIME multipart uploads wh=
en the HTTP transfer is chunked. It generates an Erlang exception.

I spent the weekend trying to implement multipart document+attachment uploa=
ds in my client code. In doing so I ran into what I think is a bug in Couch=
DB =97 after I=92d gotten the client side working, every upload produced an=
 Erlang exception on the server. I tried changing around the client-side co=
de so it precomputed the body length instead of sending the body in =91chun=
ked=92 encoding, and that made CouchDB happier.

The exception looks like:

[error] [emulator] Error in process <0.15079.3> with exit value: {badarith,=
[{couch_httpd_db,'-receive_request_data/2-fun-0-',3},{couch_httpd,read_unti=
l,3},{couch_httpd,parse_part_body,1},{couch_httpd,parse_multipart_request,3=
},{couch_doc,'-doc_from_multi_part_stream/2-fun-1-'...=20

Is this a known bug, or should I file something?

=97Jens

* Well, Couchbase Single Server 2.0.0dev4, which I think is basically Couch=
DB 1.1.1.