EldoS | Feel safer!

Software components for data protection, secure storage and transfer

TElClientIndySSLIOHandlerSocket & SOCKS4/4A/5

Also by EldoS: Solid File System
A virtual file system that offers a feature-rich storage for application documents and data with built-in compression and encryption.
Posted: 12/02/2013 12:12:47
by David  (Basic support level)
Joined: 12/02/2013
Posts: 2

Please provide solution on how to use TElClientIndySSLIOHandlerSocket with SOCKS 4/4A/5

I get connection closed gracefully when using with TIdHTTP. With OpenSSL this doesn't happen. I am using XE4 Update 1.
Posted: 12/03/2013 01:54:27
by Ken Ivanov (EldoS Corp.)

Hello David,

Thank you for getting in touch with us.

We will try to reproduce the issue locally and get back to you shortly.

A side question, Is there anything that forces you to use the Indy I/O handler descendant and not the `native` TElHTTPSClient class, which is more powerful and feature-rich and for which we are fully responsible?
Posted: 12/03/2013 02:06:16
by David  (Basic support level)
Joined: 12/02/2013
Posts: 2


You can use software such as CCProxy to test various proxy implementations. SOCKS4/5. By the way HTTP proxies work with TElClientIndySSLIOHandlerSocket.
Posted: 12/03/2013 03:30:40
by Vsevolod Ievgiienko (EldoS Corp.)

Indeed the problem exists.

Please go to SBIndyIOHandler10.pas:TElClientIndySSLIOHandlerSocket.ConnectClient method and change its code next way to fix it:

procedure TElClientIndySSLIOHandlerSocket.ConnectClient;
  LPassThrough: Boolean;
  LPassThrough := fPassThrough;
  fPassThrough := True;
    inherited ConnectClient;
    fPassThrough := LPassThrough;

  if not Passthrough then

This improvement will be also included into the next SBB build.



Topic viewed 510 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!