HTTPClientInvoker does not support BASIC authentication for proxies when use of proxy is configured by system properties ------------------------------------------------------------------------------------------------------------------------ Key: JBREM-1050 URL: https://jira.jboss.org/jira/browse/JBREM-1050 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 The use of a proxy can be communicated to the HTTP transport in two ways. 1. The parameters "http.proxyHost" and "http.proxyPort" can be configured in the invocation metadata map, or 2. the system properties "http.proxyHost" and "http.proxyPort" can be set. In the former case, org.jboss.remoting.transport.http.HTTPClientInvoker will attempt to call java.net.URL.openConnection(java.net.Proxy) (which exists only in jdk 1.5 and above). If the call succeeds, HTTPClientInvoker will go on to create a "Proxy-Authorization" request header, based on the values associated with ""http.proxy.username" and "http.proxy.password", either in the invocation metadata map or as system properties. In the latter case, the java.net.URL class will configure proxy information based on the system properties. The problem is that, in the latter case, HTTPClientInvoker does not check for the existence of the "http.proxyHost" and "http.proxyPort" system properties, and so never checks to see if it should create a "Proxy-Authorization" request header. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira