[ https://issues.jboss.org/browse/JBIDE-11603?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11603: ------------------------------------------ PROD (openshift.redhat.com) and STAGE (stg.openshift.redhat.com) currently dont support version negotiation. You get 406 NOT accepted if you add the version specification to the Accept header: {quote} curl -k --user "<ACCOUNT>:<PASSWORD>" -H "Accept: application/json;version=1.0" https://openshift.redhat.com/broker/rest/cartridges -v < HTTP/1.1 406 Not Acceptable < Date: Wed, 25 Apr 2012 09:01:10 GMT < Server: Apache/2.2.15 (Red Hat) < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.4 < X-Runtime: 0.920704 < Cache-Control: no-cache < X-UA-Compatible: IE=Edge,chrome=1 < Status: 406 < Strict-Transport-Security: max-age=15768000, includeSubDomains < Content-Type: text/html; charset=utf-8 < Vary: Accept-Encoding,User-Agent < ProxyTime: D=946495 < Connection: close < Transfer-Encoding: chunked < * Closing connection #0 {quote} I therefore cannot enable version negotiation to the client library, we'd end up with a non-functional client-lib for now. I added version negotiation but commented the code that would add it to the Accept-header. I also @Ignore'd the tests for it. According to the openshift team version negotiation will make it to productin next monday. That's unfortunately too late for us since we freeze on friday, we might have to deploy a new client version after our freeze. I furthermore found a version negotiation approach that is obviously compatible to the current PROD/STG. It would just require us to indicate the required version in a slightly different manner (that is IMHO RFC compliant - whereas their current approach is not IMHO): {quote} Accept: application/json;q=1,version=1.0 {quote} (note the media type quality indicator in between the media type and the version. The version becomes accept-extension (a secondary media type qualifier) as state in the RFC (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). I dont know if this alternative would be parsed correctly by the new broker. The response is currently still pending. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11603?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11603: ------------------------------------- Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta3) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11603?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11603: ------------------------------------------ version negotiation is finally supported on PROD. I enabled the version negotiation in the client lib (and enabled the tests for it), built a new jar a copied it into our client plugin. Committed to TRUNK (CR1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11603?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-11603. ---------------------------------- Verified on github. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira