[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15830 at 11/13/13 11:34 AM: --------------------------------------------------------------------- The useragent is set via a properties file: {code:title=RestService (constructor)} setupClient(properties.getUseragent(clientId), protocolVersion, acceptedMediaType, client); {code} The properties file that shipped with the client library has the useragent that we're using in OpenShift. The properties file allows the maven build to substitute the plugin version in the user-agent: {code:title=src\/main\/resources\/restservice.properties} useragent=Java OpenShift REST/{0} ({1}) {code} To my current understanding you should be able to override the user-agent by providing your own restservice.properties. This would then in turn allow us to remove the magic code (discussed above) that mangles the useragent when keys are present. was (Author: adietish): The useragent is set via a properties file: {code:title=RestService (constructor)} setupClient(properties.getUseragent(clientId), protocolVersion, acceptedMediaType, client); {code} The properties file that shipped with the client library has the useragent that we're using in OpenShift. The properties file allows the maven build to substitute the plugin version in the user-agent: {code:src/main/resources/restservice.properties} useragent=Java OpenShift REST/{0} ({1}) {code} To my current understanding you should be able to override the user-agent by providing your own restservice.properties. This would then in turn allow us to remove the magic code (discussed above) that mangles the useragent when keys are present. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira