couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <rnew...@apache.org>
Subject Re: Problems with multipart attachment updates
Date Mon, 13 Aug 2012 19:57:35 GMT
Attachments are not stored with base64 encoding, nor are they base64 encoded in a multipart
PUT (that's part of the reason that this API and the 'standalone attachment API' is more efficient).

I glanced at this earlier but didn't see anything obviously wrong. If the boundary is malformed,
that would do it, among other things.

B.

On 13 Aug 2012, at 20:15, Jens Alfke wrote:

> 
> On Aug 13, 2012, at 7:15 AM, Julian Goacher <julian.goacher@innerfunction.com>
wrote:
> 
>>   [Mon, 13 Aug 2012 14:10:02 GMT] [error] [<0.6811.10>] Uncaught error
>>   in HTTP request: {error,undef}
>>   [Mon, 13 Aug 2012 14:10:02 GMT] [info] [<0.6811.10>] Stacktrace:
>>   [{base64,encode,
>>   [<<115,176,77,34,80,64,240,8,14,182,224,
>>   181,170,42,191,128>>],
>>                                          []},
>>   {couch_doc,'-to_json_attachments/4-fun-0-',
>>                                          4,
> 
> It looks like CouchDB is failing to base64-encode some data, which presumably would be
the contents of your attachment, except that the values in the "<<"-delimited binary
string are total garbage if interpreted as ASCII. That's as much as I can make out without
a good knowledge of the innards of CouchDB…
> 
> Your request looks fine to me.
> 
> —Jens


Mime
View raw message