[
https://issues.apache.org/jira/browse/AXIS2-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tejas mehendale updated AXIS2-6044:
---
Description:
Refer classes ->
org.apache.axis2.transport.http.impl.httpclient4.HTTPProxyConfigurator
-> method -> configure
Also,
org.apache.axis2.transport.http.impl.httpclient3.HTTPProxyConfigurator ->
method -> configure
1 -
In this method , axis2.xml configuration file is referred 1st for proxy
settings which is overridden if set by messageContext proxy properties which is
overridden by system property if set for proxy settings
now, lets say we have multiple integrations in our system and few of
integrations use system level proxy settings and few other require some other
proxy setting depending on flow/input then , this is not possible to achieve
since system properties ultimately overrides what is set in message context
we think that precedence should be like , check 1st system properties if set
then if axis2 configuration is set then override system properties and then
check. if messageCOntext proxy properties is set then it should be used
overriding axis2 config. properties or system properties , that way when a
system is calling multiple integration points that system get to choose which
proxy setting is used by an integration be setting proxy settings in
messageContext property
2 -
2nd issue is -> for point 1 above for system properties , it does not consider
https.proxyHost and https.proxyPort from system properties it checks only
"http" system properties and not "https" , need support for same
was:
Refer classes ->
org.apache.axis2.transport.http.impl.httpclient4 -> method -> configure
Also,
org.apache.axis2.transport.http.impl.httpclient3 -> method -> configure
1 -
In this method , axis2.xml configuration file is referred 1st for proxy
settings which is overridden if set by messageContext proxy properties which is
overridden by system property if set for proxy settings
now, lets say we have multiple integrations in our system and few of
integrations use system level proxy settings and few other require some other
proxy setting depending on flow/input then , this is not possible to achieve
since system properties ultimately overrides what is set in message context
we think that precedence should be like , check 1st system properties if set
then if axis2 configuration is set then override system properties and then
check. if messageCOntext proxy properties is set then it should be used
overriding axis2 config. properties or system properties , that way when a
system is calling multiple integration points that system get to choose which
proxy setting is used by an integration be setting proxy settings in
messageContext property
2 -
2nd issue is -> for point 1 above for system properties , it does not consider
https.proxyHost and https.proxyPort from system properties it checks only
"http" system properties and not "https" , need support for same
> HTTPProxyConfigurator system property takes precedence over axis
> configuration and message context proxy properties
> ---
>
> Key: AXIS2-6044
> URL: https://issues.apache.org/jira/browse/AXIS2-6044
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.9
>Reporter: tejas mehendale
>Priority: Blocker
>
> Refer classes ->
> org.apache.axis2.transport.http.impl.httpclient4.HTTPProxyConfigurator
> -> method -> configure
> Also,
> org.apache.axis2.transport.http.impl.httpclient3.HTTPProxyConfigurator ->
> method -> configure
> 1 -
> In this method , axis2.xml configuration file is referred 1st for proxy
> settings which is overridden if set by messageContext proxy properties which
> is overridden by system property if set for proxy settings
> now, lets say we have multiple integrations in our system and few of
> integrations use system level proxy settings and few other require some other
> proxy setting depending on flow/input then , this is not possible to achieve
> since system properties ultimately overrides what is set in message context
> we think that precedence should be like , check 1st system properties if set
> then if axis2 configuration is set then override system properties and then
> check. if messageCOntext proxy properties is set then it should be used
> overriding axis2 config. properties or system properties , that way when a
> system is calling multiple integration points that system get to choose which
> proxy setting is used by an integration be setting proxy settings in
> messageContext property
> 2 -
> 2nd issue is -> for point 1 above for system properties , it does not
> consider https.proxyHost and https.proxyPort from sy
