Hi, regarding the http proxy. I've tried out the your suggestion. I also found this jira https://issues.apache.org/jira/browse/SYNAPSE-481.
Look like the issue was closed on 12/Mar/09 04:58 PM and the latest release is from 9-Jun-2008. It looks to me that the fix is not included in any official release. I've got one additional question - how do I turn on logging in different locations around the project(for example the NIO HTTP sender)? Regards Regards, Angel Tcholtchev STREAM SOA INTEGRATION SAP AG Bulgaria On Fri, Mar 5, 2010 at 11:47 AM, Ruwan Linton <[email protected]>wrote: > Hi Angel, > > Please use the following parameters in the http transport sender > configuration in the axis2.xml; > > <transportSender name="http" > class="org.apache.synapse.transport.nhttp.HttpCoreNIOSender"> > <parameter name="non-blocking" locked="false">true</parameter> > <parameter name="http.proxyHost" locked="false">$host</parameter> > <parameter name="http.proxyPort" locked="false">$port</parameter> > <parameter name="http.proxyUser" locked="false">$user</parameter> > <parameter name="http.proxyPassword" locked="false">$pwd</parameter> > > </transportSender> > > Thanks, > Ruwan > > On Fri, Mar 5, 2010 at 1:26 PM, Angel Tcholtchev < > [email protected]> wrote: > > > Hi, > > I'm using synapse as proxy service. The actual back-end requires http > basic > > authentication. The endpoint is also not directly reachable from my > > network, > > so I have to set a http proxy to successfully call it. > > I searched through the synapse documentation but I could not find how to > > set > > "out of the box" these properties to the axis2 http transport. Can you > > please help me? > > > > > > Regards, > > Angel > > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: [email protected]; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com >
