I am updating a Delphi legacy application which uses OverbyteIcs. The version 
is not confirmed but I believe it is v6. The package the legacy Delphi 
application uses is OverbyteIcsBcb100Package.bpl.

This Delphi app successfully uses HTTPCli to download data via HTTP, and in 
particular can download data via the NTLM security protocol. I am migrating the 
Delphi app to C++ and all is well apart from the ability to download data using 
the HTTPCli with NTLM configured.

The old version of the application written in Delphi, which can successfully 
handle NTLM, uses the following 2 lines when NTLM is in use:
ipsHTTPS.UseWinInet  := True;
ipsHTTPS.ProxyServer := '*' + HTTPProxyUser + '*' + HTTPProxyPass;

My latest application written in C++, which cannot handle NTLM, uses the 
following lines when NTLM is in use: 
HttpCli->ProxyAuth = httpAuthNtlm;
HttpCli->ProxyUsername = HTTPProxyUser;
HttpCli->ProxyPassword = HTTPProxyPass;

1) Should the UseWinInet option be available in the C++ version?
2) Are the '*' used in Delphi version for ProxyServer interpreted by Overbyte 
or are these characters recognised by MS NTLM?

Arno has advised me to update to v7, however I am encountering a number of 
issues migrating. In particular it surrounds the Record Alignment settings and 
the necessity for my application to use Byte alignment instead of Word 
alignment as is the default setting for OverbyteIcsv7. I would prefer to 
utilise the existing package.

Thanks in advance for any support or information


This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored. Internet 
communications cannot be guaranteed to be secure or error-free as information 
could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
contain viruses. Therefore, we do not accept responsibility for any errors or 
omissions that are present in this message, or any attachment, that have arisen 
as a result of e-mail transmission. If verification is required, please request 
a hard-copy version. Any views or opinions presented are solely those of the 
author and do not necessarily represent those of the company.
To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to