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 <[email protected]> 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 <[email protected]> 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 <[email protected]> > > wrote: > > > > > On Tue, Mar 25, 2014 at 1:19 PM, JC de Villa <[email protected]> > > wrote: > > > > curl -X PUT -H 'Content-Type: multipart/related; boundary="abc123"' > > > > http://localhost:5984/odms_contents/abc [email protected] > > > > > > 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
