I need to operate my web service over ssl secured https. The service works fine over http, the overall app works fine over https. I have so far only configured the tomcat for https://myserver.example.com:8443/
The recommended config http://cwiki.apache.org/CXF20DOC/client-http-transport.html I don't understand as it seems to hard code the URLs for the service which I avoid by using the CXFServlet. It also seems to configure the keystore again, duplicating things that are already done in tomcat. And in addition the example does refer to authenticating via tls over ssl and I don't do that. The service authendicated to our app via WS-I Base profile Interceptors. Here is the behavior that I can't get around: The CXFServlet from 2.0.11 does serve its top level list of services under the URL https://myserver.example.com:8443/soap-services/ However, the URLS to the WSDL for each service is not https:// ==> http://myserver.example.com:8443/soap-services/my-service?wsdl and when I click on the link it does offer to save a binary file. When I manually request https://myserver.example.com:8443/soap-services/my-service?wsdl I get the file but it's <soap:address location="http://myserver.example.com:8443/soap-services/my-service"/> is http again and that fails to import then any xsd files. Any idea what to do to work around this? -- View this message in context: http://www.nabble.com/CXFServlet-over-https-tp25703630p25703630.html Sent from the cxf-user mailing list archive at Nabble.com.
