Hello Jaro, Searched the history and came across
http://www.nabble.com/problem-with-redirect-http-request-to-https-td21438244.html#a21443997 I could not figure out any other messages that seems appropriate. If I got it right, you are telling that the fix is included in trunk now. The error I received previously was the one stated on http://www.nabble.com/CXF-and-Java-6-Update-10-td19463818.html#a20690343 and I updated cxf to 2.1.4 afterwards. Also, the tlsclientparameters did not cause any problems regarding using both http & https on different instances on runtime. regards, Alp On Fri, Feb 27, 2009 at 3:55 PM, Jaroslav Libak <[email protected]> wrote: > This problem has been discussed on this list before, just see history. I > also > posted a patch that allows you to use both http and https for WSDL, once > you > have https parameters configured (if you don't, then https is not allowed). > > I think that using > http.setTlsClientParameters(new TLSClientParameters()); > > on the fly per request basis is not thread safe. You might get problems if > 1 > thread needs to call http, and 2nd https web service. > > Jaro > > Alp Timurhan Çevik schrieb: > > Hello, > > > > I am experiencing a difficulty with HTTP-HTTPS. > > > > I am calling some web services, which have both HTTP and HTTPS endpoints > on > > the test system. I would like to call both protocols, based on a > parameter > > supplied from the data, which is supplied before calling the web service. > > > > I was happily able to do that, until I started using 1.6.0.11. I was > using > > 1.6.0.6 or smth previously. As soon as I started using v11, I received an > > exception. Googling it out, I found out that the problem was due to some > web > > service method changes, introduced in 1.6.0.10, thus I needed to use cxf > > version > 2.1. No big deal, downloaded 2.1.4 and started working with it, > as > > I have some thin clients that have some roms which have only v11. > > > > After starting to use jre 1.6.0.11 and cxf 2.1.4, I started receiving > > another exception, which is, > > > > java.io.IOException: Illegal Protocol http for HTTP URLConnection > Factory. > > > > I had setup > > > > http.setTlsClientParameters(new TLSClientParameters()); > > http.getTlsClientParameters().setSecureSocketProtocol("SSL"); > > http.getTlsClientParameters().setDisableCNCheck(true); > > http.getTlsClientParameters().setTrustManagers(getDummyTrustManager()); > > > > previously, prior to changing the jre. > > > > Googling out the exception, > > > > http.getTlsClientParameters().setSecureSocketProtocol("SSL"); > > > > was the required row, but I already had it running. > > > > So searching some more, I came across some article stating that the wsdl > > adress should include https if I needed to call https adresses. I have > some > > 50 wsdls to connect to, but I have changed the location parameter in > wsdls > > using some ant scripting. I was able to call https later on, but unable > to > > call http, receiving > > > > java.io.IOException: Illegal Protocol http for HTTPS URLConnection > Factory. > > > > now. > > > > What I need is something that can change the urlconnectionfactory after > > instantiation, not only at the time of reading the wsdl. > > > > Tried to use JaxWsClientProxyBean, but was not very successful, as I need > > tlsclientparameters and also some other parameters, and also I need the > > adress from the original wsdl, which I later modify according to the > > protocol requested. > > > > Thanks a lot for your time, > > Alp > > > >
