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 jc.devilla@gmail.com
 designates 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGHTdUXZuY7N9uz=QxsNvfA0J9_98Ctduf-X4S6_EHCyyj8Hew@mail.gmail.com>
References: 
 <CAOvw+NYLZYV3Y0kqcaWQDdYnEWY3FRRVgGVZwrWsrKwpx8r98w@mail.gmail.com>
	<CAHdjipJ+Sg_3R8Fb1dQSWP-ABxxfhK-KWtqkj_hd1k7qzT=7xQ@mail.gmail.com>
	<CAOvw+NY2rkZMEcg0ugNQ+D6_2jDVhVrOX-9+QzmubgqONFK1hQ@mail.gmail.com>
	<CAHdjipJs+1gFKhZb3y--41DAmCrBXDBEDxCj_7ynq1JovYabRg@mail.gmail.com>
	<CAOvw+NbzJ2asPGADZrrAeyKVQG=C7ws18atjCQeAdU49RvuZQA@mail.gmail.com>
	<CAGHTdUWirGM=0tbFArS5A=bYbFcv=gJjd6nSMEp+VPeTr9v5JQ@mail.gmail.com>
	<CAOvw+NZWz7-_qynVgQxchWg5vgSQUmDKE0xdQrdqJ7gFVaODgw@mail.gmail.com>
	<CAGHTdUXZuY7N9uz=QxsNvfA0J9_98Ctduf-X4S6_EHCyyj8Hew@mail.gmail.com>
Date: Tue, 25 Mar 2014 18:31:26 +0800
Message-ID: 
 <CAOvw+NYZgz1Abt7jDMocRj+o1G2J6k=jUHRmRxnc8z5yU7+z4w@mail.gmail.com>
Subject: Re: Uploading attachments using Multipart/related
From: JC de Villa <jc.devilla@gmail.com>
To: CouchDB Mailing List <user@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3d864bc357604f56bda16

--001a11c3d864bc357604f56bda16
Content-Type: text/plain; charset=ISO-8859-1

Thanks Nick, much appreciated.


On Tue, Mar 25, 2014 at 6:20 PM, Nick North <north.n@gmail.com> wrote:

> Sounds as if that should work then. I'm not much of a curl user, so don't
> know if there are any other potential problems in the command line. I'm not
> around my CouchDb installations today, but I can construct a working
> request this evening if no-one else beats me to it.
>
> Nick
>
>
> On 25 March 2014 09:56, JC de Villa <jc.devilla@gmail.com> wrote:
>
> > I had the same thought in that it might be the parser complaining about
> > formatting, and I've made sure that it matches the example exactly.
> >
> >
> > On Tue, Mar 25, 2014 at 5:52 PM, Nick North <north.n@gmail.com> wrote:
> >
> > > Do you have the same initial line breaks as in the example? I can't
> > > remember the exact details at the moment, but mime parsing can be
> > sensitive
> > > about that and, if you are missing the line break before the first
> > boundary
> > > string, it might skip over the JSON body.
> > >
> > > Nick
> > >
> > >
> > > On 25 March 2014 09:25, JC de Villa <jc.devilla@gmail.com> wrote:
> > >
> > > > Hmm,
> > > >
> > > > I get the same using -T and --data-binary (tried again just now).
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Mar 25, 2014 at 5:22 PM, Alexander Shorin <kxepal@gmail.com>
> > > > wrote:
> > > >
> > > > > On Tue, Mar 25, 2014 at 1:19 PM, JC de Villa <jc.devilla@gmail.com
> >
> > > > wrote:
> > > > > > curl -X PUT -H 'Content-Type: multipart/related;
> boundary="abc123"'
> > > > > > http://localhost:5984/odms_contents/abc -d@test.data
> > > > >
> > > > > That's the problem. -d sends data as text. you should use
> > > > > --data-binary or -T argument to send it as binary.
> > > > >
> > > > > --
> > > > > ,,,^..^,,,
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > JC de Villa
> > > >
> > >
> >
> >
> >
> > --
> > JC de Villa
> >
>


-- 
JC de Villa

--001a11c3d864bc357604f56bda16--