indy ssl handshake/certificate chain not available

Article View: borland.public.cppbuilder.internet.socket

Article #5236

Back to borland.public.cppbuilder.internet.socket Previous Next

#5236

From: lai
Date: Fri, 24 Sep 2004 15:07

9 lines
1269 bytes

Hi, I just built a http server unsing b++6 (indy 8) that runs as a windows service.
the client side issues http, which is j2me application running on blackberry device
Now we want to change to https from client side to secure.
I add TIdServerInterceptOpenSSL component and specify cert, key and rootcert file sloacation.
Then I always get certificate chain not available. It looks like the server certificate not sent to client.
Since this indy ssl stuff is new to me, is there anyone can help me?
Thanks,
Lynn

Technical Details

Message-ID: <4154384a$1@newsgroups.borland.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Thread: 11508e,2c83ca58ae664c04,start
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: <lai@eagency.com>
Sender: lai@eagency.com
Reply-To: <lai@eagency.com>
Subject: indy ssl handshake/certificate chain not available
Newsgroups: borland.public.cppbuilder.internet.socket
X-User-Info: 65.218.213.100     
NNTP-Posting-Host: 207.105.83.66
Message-ID: <4154384a$1@newsgroups.borland.com>
Date: 24 Sep 2004 08:07:54 -0700
X-Trace: newsgroups.borland.com 1096038474 207.105.83.66 (24 Sep 2004 08:07:54 -0700)
Lines: 9
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail