Using INDY With A Secure Proxy (HTTPS)

Hi,

You can try:

TIdTCPClient/Server with SSL
http://www.indyproject.org/Sockets/Demos/index.en.aspx

download sample from http://adg.bmpcoe.org/IndySSL/
(from site:
SSL CLIENT:
This program is a simple TCP Client that makes an SSL connection on port 3000. To connect to a server, enter the IP address of the server in the box labeled "Host:", and then press the "Connect" button. Once a connection has been established, the client displays any text received from the server in the memo area. To send text to the server, enter it in the available edit box, and then press [enter].

SSL SERVER:
This program establishes a TCP Server that listens for SSL connections on port 3000. When a connection is received, the server responds with "Hello", and then listens for any other lines of text sent from the client. When a line is received, it is echoed to the screen as well as back to the client.

See note present on the site about required dll's).

another previous contributions
http://www.experts-exchange.com/Programming/Languages/Pascal/Delphi/Q_22095668.html
still open (Need to get SSL working correctly with indy 10 - specifically the TIDHTTP component)
http://www.experts-exchange.com/Programming/Languages/Pascal/Delphi/Q_22087897.html

Download also the help file (pdf format - more than 3000 pages).
You can read useful infos:


TIdServerInterceptOpenSSL
Implements Secure Sockets Layer support for Indy Server Intercept components.
Description
The TIdServerInterceptOpenSSL server intercept class implements the Open SSL implementation of Secure Sockets Layer
through support .DLL's available at http://www.intelicom.si/. You have to deploy these support .DLL's in order to use this
component's functionality in your application. To do this, we recommend that you install the .DLL's in the user's system directory.
Indy does not give you any legal rights to use SSL. Some nations including the U.S. regulate or prohibit the export of strongencryption
such as SSL. In addition, using SSL in some nations may be illegal. It is up to you to determine the legal situation in
your nation.

OnGetPassword
Event type for password retrieval.
Description
OnGetPassword is an event that requests the password for unlocking the private key stored in a file. You can simply set the
Password variable with the proper password or you can add some dialog box that prompts user for the password.
procedure TForm1.IdServerInterceptOpenSSL1GetPassword(var Password: String);
begin
Password := 'aaaa';
end;

OnStatusInfo
Provides status information for an SSL connection.
Description
OnStatusInfo is an event that can be used for debugging the connection establishment. It sends a message (Msg) with current
status.
procedure TForm1.IdServerInterceptOpenSSL1StatusInfo(Msg: String);
begin
ShowMessage(Msg);
end;


OnVerifyPeer
Event type for peer X.509 certificate verification.
Description
OnVerifyPeer is an event that can be used for peer checking. The events passes the TIdX509 structure (certificate ) that
embeds the values of peer's certificate. You can read certificate time restrictions, issuer name, subject name.
The result value signals if you are pleased with peer's info. If you return False then the connection will be dropped, elsewhere
you will keep the connection.
function TForm1.IdServerInterceptOpenSSL1VerifyPeer(
Certificate: TIdX509): Boolean;
begin
ShowMessage(DateTimeToStr(Certificate.notBefore));
ShowMessage(Certificate.Issuer.OneLine);
ShowMessage(Certificate.Subject.OneLine);
Result := True;
end;


TIdCustomHTTPServer is a TIdTCPServer descendant that specifies properties, methods, and events for an implementation
of the Hypertext Transfer Protocol (HTTP) as described in the Internet Standards document:
RFC 1945 - Hypertext Transfer Protocol [HTTP] version 1.0 (http://www.rfc-editor.org/rfc/rfc1945.txt)
RFC 2616 - Hypertext Transfer Protocol [HTTP] version 1.1 (http://www.rfc-editor.org/rfc/rfc2616.txt)
Application do not normally create instances of TIdCustomHTTPServer. Most properties, methods, and events in
TIdCustomHTTPServer are protected to allow descendant classes to override their implementaion. Use TIdHTTPServer to
access published properties, method, and events.
TIdCustomHTTPServer also supports the Secure Hypertext Transport protocol (HTTPS) as described in the Internet Standards
document:
RFC 2660 - The Secure HyperText Transfer Protocol (http://www.rfc-editor.org/rfc/rfc2660.txt)
Assign an instance of TIdServerInterceptOpenSSL to the Intercept property to allow use of the HTTPS protocol. For the
Windows platform, you must install the Indy OpenSSL support .DLL's available at http://www.intelicom.si to enable Secure
Socket Layer support.

.....

etc, etc, ....

Hope this can help a little.