You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Kristian Rink <ka...@googlemail.com> on 2011/10/12 13:47:05 UTC
HTTP 400 in POST without _id on 1.0.2?
Folks;
not sure this is a real problem or just a misconfiguration /
misunderstanding of sorts: We do have an application built using Java
and, right now, the ektorp CouchDB client. In one part obviously
CouchDB documents are to be created, and in all situations the
documents POSTed to the CouchDB contain no _id, expecting to have one
assigned automatically.
We ran this on three machines:
Linux (Ubuntu 11.10 pre) workstation, CouchDB 1.0.1: Works.
Testbed server (Ubuntu 11.04), CouchDB 1.0.1: Works.
Another development workstation, Windows 7, CouchDB 1.0.2: Doesn't
work. This is the error found in couch.log after raising log level to
DEBUG:
---- snip ----
[Wed, 12 Oct 2011 11:43:03 GMT] [debug] [<0.106.0>] Document id is not
a string: null
[Wed, 12 Oct 2011 11:43:03 GMT] [debug] [<0.106.0>] Minor error in HTTP
request: {bad_request,<<"Document id must be a string">>}
[Wed, 12 Oct 2011 11:43:03 GMT] [debug] [<0.106.0>] Stacktrace:
[{couch_doc,validate_docid,1},
{couch_doc,transfer_fields,2},
{couch_httpd_db,db_req,2},
{couch_httpd_db,do_db_req,2},
{couch_httpd,handle_request_int,5},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]
---- snip ----
The (client) code is the same in all these situations, only difference
seems to be the OS platform and the version of CouchDB. Does that make
sense to anyone out there?
TIA and all the best,
Kristian
--
Kristian Rink
http://dm.zimmer428.net
http://twitter.com/kr428
Re: HTTP 400 in POST without _id on 1.0.2?
Posted by Robert Newson <rn...@apache.org>.
Can you show the exact document body you are sending in the request?
On 12 October 2011 12:47, Kristian Rink <ka...@googlemail.com> wrote:
> Folks;
>
> not sure this is a real problem or just a misconfiguration /
> misunderstanding of sorts: We do have an application built using Java
> and, right now, the ektorp CouchDB client. In one part obviously
> CouchDB documents are to be created, and in all situations the
> documents POSTed to the CouchDB contain no _id, expecting to have one
> assigned automatically.
>
> We ran this on three machines:
>
> Linux (Ubuntu 11.10 pre) workstation, CouchDB 1.0.1: Works.
>
> Testbed server (Ubuntu 11.04), CouchDB 1.0.1: Works.
>
> Another development workstation, Windows 7, CouchDB 1.0.2: Doesn't
> work. This is the error found in couch.log after raising log level to
> DEBUG:
>
> ---- snip ----
> [Wed, 12 Oct 2011 11:43:03 GMT] [debug] [<0.106.0>] Document id is not
> a string: null
>
> [Wed, 12 Oct 2011 11:43:03 GMT] [debug] [<0.106.0>] Minor error in HTTP
> request: {bad_request,<<"Document id must be a string">>}
>
> [Wed, 12 Oct 2011 11:43:03 GMT] [debug] [<0.106.0>] Stacktrace:
> [{couch_doc,validate_docid,1},
> {couch_doc,transfer_fields,2},
> {couch_httpd_db,db_req,2},
> {couch_httpd_db,do_db_req,2},
> {couch_httpd,handle_request_int,5},
> {mochiweb_http,headers,5},
> {proc_lib,init_p_do_apply,3}]
> ---- snip ----
>
> The (client) code is the same in all these situations, only difference
> seems to be the OS platform and the version of CouchDB. Does that make
> sense to anyone out there?
>
> TIA and all the best,
> Kristian
>
>
> --
> Kristian Rink
> http://dm.zimmer428.net
> http://twitter.com/kr428
>