Oleg,
thanks for taking care.
What about my concern regarding
"ctx.contextSpi.trustManager" pointing to
"com.sun.net.ssl.internal.ssl.DummyX509TrustManager" ?
I have checked with the CURL utility in detail and compared it with a
successfull connection to some external
HTTPS- server and I guess there is an issue with the server. I donn't want
to bother you with details, but
the connection is broken once in the handshake procedure.
>....
* HTTP 1.0, assume close after body
< HTTP/1.0 401 Unauthorized
< WWW-Authenticate: Digest
realm="HTTPAccess",nonce="8BF95ABC4212FD4976EF5382AE58865E",algorithm="MD5",qop=
<
* SSLv3, TLS alert, Client hello (1):
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
* Issue another request to this URL:
'https://192.168.111.56/cgi-bin/xml/read?Meter.1'
* About to connect() to 192.168.111.56 port 443 (#0)
* Trying 192.168.111.56... connected
* Connected to 192.168.111.56 (192.168.111.56) port 443 (#0)
...
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES128-SHA
* Server certificate:
Let me clarify this first with the supplier of the server (or if you have
an idea, let me know...)
> If you can reproduce the problem with a test app that can be executed
> outside your local environment I'd happily take a look at it.
Thanks, much appreciated. Unfortunately, the server is inside our
companies LAN.
I'll try to arrange somehow to get the firewalls temporarely opened for
this incident.
Coming back with details if I got the permission.
Regards
/Gerd
The information included in this e-mail and any files transmitted with it is
strictly confidential and may be privileged or otherwise protected from
disclosure. If you are not the intended recipient, please notify the sender
immediately by e-mail and delete this e-mail as well as any attachment from
your system. If you are not the intended recipient you are not authorized to
use and/or copy this message and/or attachment and/or disclose the contents to
any other person.
