On Tue, Nov 24, 2009 at 13:56, Moritz Mädler <m...@moritz-maedler.de> wrote: > Hi Andreas! > > Thanks for your quick reply. > > Is it fixed in the 1.5.1 release, too?
No, it is scheduled for 1.6. > If we discard the unsecured address and only provide the https-address is > there a way to set it "by hand"? I'm not sure that I understand the idea. Can you explain a bit further? > Thanks alot! > > > > >> This is probably yet another instance of the issue described in >> AXIS2-4465 (which is fixed in trunk). >> >> Andreas >> >> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <m...@moritz-maedler.de> wrote: >>> Hi, >>> >>> we want to provide our service also via SSL. >>> Our Axis 1.5 runs as an application in Tomcat 6 which we already configured >>> for listening for SSL-Connections. >>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as >>> https://serviceurl:80/SERVICE. This is not >>> working as the Port 80 is added misleadingly. >>> I don't know how to fix that and especially keep both transports http and >>> https as we want to use the old clients >>> were we could not change the address to the new https one. >>> >>> I hope you can help!? >>> >>> >>> Thanks alot! >>> >>> Moritz > >
