Am Montag, 9. April 2012, 19:41:30 schrieb Charles Duffy:
Howdy --
The following is arguably a bug in my REST bindings rather than the server, but it worked as of the 7.2 release but fails as of the current 7.2.1 snapshot.
A request akin to the following:
POST /rest HTTP/1.1 Host: 127.0.0.1:8984 Content-Length: 86 Authorization: Basic cmVhZG9ubHk6cmVhZG9ubHk= Content-Type: application/x-www-form-urlencoded Accept-Encoding: identity, deflate, compress, gzip Accept: */* User-Agent: python-requests/0.10.6
<rest:query xmlns:rest="http://basex.org/rest ">rest:text1+1</rest:text></rest:query>
Yields the following response:
HTTP/1.1 400 Bad Request Content-Length: 40 Server: Jetty(6.1.26)
Unknown option '<REST:QUERY XMLNS:REST'.
...but did not do so previously.
I sent some changes in the REST interface yesterday - you may try them. Basically HTTP 400 is almost alwayst thrown by the REST implementation when something is wrong (500 not that much ;) ). In my patch, I've also added more debug messages so that if you enable the debug flag it's be more easy to find the reason for the error.
Regards, Dimitar