[ 
https://issues.apache.org/jira/browse/AXIS2-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Afkham Azeez resolved AXIS2-4131.
---------------------------------

    Resolution: Incomplete

Resolving this since there has been no activity for over 2 years

> Java http proxy settings override programmatic settings
> -------------------------------------------------------
>
>                 Key: AXIS2-4131
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4131
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Devin Rosenbauer
>            Assignee: Andreas Veithen
>            Priority: Minor
>
> My code:
> Options options = stub._getServiceClient().getOptions();
>               
> HttpTransportProperties.ProxyProperties pp = 
> new HttpTransportProperties.ProxyProperties();
>               
> pp.setProxyName(proxyHost);
> pp.setProxyPort(proxyPort);
>               
> options.setProperty(HTTPConstants.PROXY, pp);
> And in other code, not under my control:
> Properties p = System.getProperties( );
> if ( ( null != proxyHost ) && ( null != proxyPort ) )
> {
>             p.setProperty( "http.proxySet", "true" );
>             
>             if ( null != proxyHost )
>                 p.setProperty( "http.proxyHost", proxyHost );
>             if ( null != proxyPort )
>                 p.setProperty( "http.proxyPort", proxyPort );
> } 
> This leads to an inexplicable failure to connect through the proxy, because 
> the second bit of code is using different proxy settings that won't work in 
> the Axis2 WS call. For now, I can work around this bug by clearing and 
> re-setting the proxy values just before I call methods in my Stub class, but 
> this is a bit silly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to