Hi All, I've tried to use the new PATCH [1] HTTP method in jclouds core but I'm getting some bizarre results.
The short story is that when I try to send a PATCH it appears to actually be sending a POST. I was sending (what I thought) was a PATCH request to Rackspace Cloud Queues but was getting the response 405 Method Not Allowed. The logging output and debugging said I was sending a PATCH. However when I ran the request through the Charles Proxy, I saw that it was actually going through as a POST, thus causing the 405 Method Not Allowed. I know that HttpURLConnection.setRequest() [2] doesn't allow PATCH. I also know that we work around this in jclouds by setting the field by reflection [3]. Has anyone else tried to use PATCH and observed this behaviour? Ignacio, have you tried PATCH yet? Thanks, Everett [1] https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/rest/annotations/PATCH.java [2] http://docs.oracle.com/javase/6/docs/api/java/net/HttpURLConnection.html#setRequestMethod(java.lang.String) [3] https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/http/internal/JavaUrlHttpCommandExecutorService.java#L182
