Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.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: Tue, 21 Aug 2012 09:02:43 -0700
Subject: Re: Base64 attachment via Futon
Thread-Topic: Base64 attachment via Futon
Thread-Index: Ac1/tmbCOpyikODRQ9a8ZSKa9DJKSA==
Message-ID: <5F64F1AA-9A7B-4552-950D-8CDF335B4F67@couchbase.com>
References: <326B8AB680B15249B86A3DB3D1FBB3EE07EA648B@NAMAIL03.sapient.com>
In-Reply-To: <326B8AB680B15249B86A3DB3D1FBB3EE07EA648B@NAMAIL03.sapient.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


On Aug 21, 2012, at 8:22 AM, Stephen Ohimor <sohimor@sapient.com> wrote:

> Context:  I'm posting a document with an attachment.  The attachment is a=
 Base64 url-safe encoded string.  I am posting to a local CouchDB server (R=
15B) via the Futon Interface.

Why use that API? My understanding is that Futon's API is considered intern=
al, and not supported.

It's quite easy to upload attachments using a regular PUT/POST to the docum=
ent URL. You can embed the base64'd attachment in the JSON, or you can post=
 in MIME multipart format and send the attachment raw.

=97Jens

PS: Also, I just noticed you said R15B =97 that's the version of *Erlang*, =
not of CouchDB. To see the CouchDB version, GET /.=