[basex-talk] Did REST interface just start enforcing Content-Type?

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:text>1+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.