Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
let's document a return value of cache wipe operation in REST interface and make it consistent between 5.0 and 4.2.
wiping the cache via REST in 5.0.0.CR4
[mlinhard@michal-linhard ~]$ curl -X DELETE -v http://test1:8080/datagrid/rest/___defaultcache * About to connect() to test1 port 8080 (#0) * Trying 192.168.11.101... connected * Connected to test1 (192.168.11.101) port 8080 (#0) > DELETE /datagrid/rest/___defaultcache HTTP/1.1 > User-Agent: curl/7.21.0 (i386-redhat-linux-gnu) libcurl/7.21.0 NSS/3.12.8.0 zlib/1.2.5 libidn/1.18 libssh2/1.2.4 > Host: test1:8080 > Accept: */* > < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Content-Length: 0 < Date: Thu, 23 Jun 2011 11:48:01 GMT < * Connection #0 to host test1 left intact * Closing connection #0
wiping the cache via REST in 4.2.2-SNAPSHOT
[mlinhard@michal-linhard ~]$ curl -X DELETE -v http://localhost:8080/infinispan-server-rest/rest/___defaultcache * About to connect() to localhost port 8080 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8080 (#0) > DELETE /infinispan-server-rest/rest/___defaultcache HTTP/1.1 > User-Agent: curl/7.21.0 (i386-redhat-linux-gnu) libcurl/7.21.0 NSS/3.12.8.0 zlib/1.2.5 libidn/1.18 libssh2/1.2.4 > Host: localhost:8080 > Accept: */* > < HTTP/1.1 204 No Content < Server: Apache-Coyote/1.1 < X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1 < Date: Thu, 23 Jun 2011 11:51:24 GMT < * Connection #0 to host localhost left intact * Closing connection #0