Https SOAPMessage fail

Question

I meet a problem about https.
I create a web project using axis, config a servlet (public class KeyResponse extends JAXMServlet implements ReqRespListener),
in the client, declare SOAPConnection conn,SOAPMessage req,resp,correct defined, resp = conn.call(req,new URL("...")), the url is the servlet above.
if the url is http ,works well,but if the url changes to https(I have config the certificate,made by keytool,when I click the web page ,the certificate is ok),
the problem comes, the call function throws exceptions , why? what's the problem?

Answer 1

Hi @ashleyparkes and Matias
Thanks a lot for the suggestions. Here is some more information
Maybe I'm missing something, what you describe sounds fundamentally flawed
2) Why redirect, why not just ajax to the right https-address? You're basically connecting to an API and should now the place.
       - It is actually the AJAX calls that fail. I tried both, with HTTP and HTTPS addresses (using JQuery). The server I m connecting to is a Proxy which makes a 302 redirect incase of an HTTP call. Now, this redirect works on a normal browser, but fails in the Embedded browser.
3) Since certificate validation is done by the Chrome embedded to CEP, it will only recognize those certs Chrome had as root CAs at the time it was embedded. Also means no selfsigned stuff (there is no "Accept untrusted server"-popup) but you'd have to get some well established commercial cert for your domain that works with Chrome 2012-2015 (Win and Mac).
4) The AJAX-layer of Chrome operates under the RFC rules (https://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#infrastructure-for-the-send%28%29-me thod) so it might behave differently from setting browser Url. For example AJAX-redirects require correct Location-header response and forbid domain changes (to avoid cross site scripting attacks).
   -  Absolutely. "there is no "Accept untrusted server"-popup", I think this could be the reason why the CEP browse blocks the requests (??). Can someone verify ?
Using Node.js sounds like a good idea (more control) if you need redirects.
- This is not possible at the moment for us, as it would interfere with our custom GUI framework. Currently we have disabled Node.js on the extension.
Thanks once again
Gayatri