Re: POST request to SSL/HTTPS URL
Dundonald wrote:
Arne I tried your solution and I couldn't get it to work, and to be
honest it was over a few hours ago now since I tried so I can't
remember which one out of the many attempts and error messages I got
today, sorry.
I tested it before posting so it is a working example.
I've done even more googling and came across the jakarta commons
httpclient package (http://jakarta.apache.org/httpcomponents/
httpclient-3.x/) and decided to give that a go. This package handles
both HTTP and HTTPS.
It solves problems with maintaining session and handling
redirects etc..
But for a simple HTTPS it should neither be necessary or
make a difference.
Again I tried it with HTTP and it worked great (see code below). I
then switched to a HTTPS connection and I get an
SSLHandshakeException, top few lines of stack trace here ...
[06/10/07 23:25:32:062 BST] 5d9100f1 SystemErr R Fatal transport
error: unknown certificate
[06/10/07 23:25:32:062 BST] 5d9100f1 SystemErr R
javax.net.ssl.SSLHandshakeException: unknown certificate
That sounds as a certificate problem. Exactly what my code was handling.
So I do some more googling and I read about adding these two lines:
System.setProperty("java.protocol.handler.pkgs",
"com.sun.net.ssl.internal.www.protocol");
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
Referring directly to com.sun classes should not be necessary.
which I do to the top of the code below and I then get a different
exception - example stack trace top few lines here ...
[06/10/07 23:28:32:562 BST] 69b640f1 WebGroup E SRVE0026E:
[Servlet Error]-[Cipher buffering error in JCE provider IBMJCE]:
java.lang.RuntimeException: Cipher buffering error in JCE provider
IBMJCE
IBMJCE ??
Are your working with an IBM Java ?
why is it so difficult to connect to SSL?
It is really not that difficult.
Arne