"dk_sz" <dk_sz@hotmail.com> wrote in message
news:45ba693a$1@newsgroups.borland.com...
> Am I correct in assuming that currently getting
> Indy to work with HTTPS requires external modules?
It requires the OpenSSL library. The latest version of Indy 10 uses
the official DLLs from http://www.openssl.org. Indy 9, and older
builds of Indy 10, used custom-built DLLs instead, which are linked to
on the Indy website.
Everything else is built into Indy.
> I was just wondering whether a non-cross-platform solution
> could be to simply wrap Inet?
Indy's SSL is generic enough to work with any connection. WinInet is
not quite so generic. Also, by using the socket API directly, Indy
provides functionality that WinInet doesn't. Also, because Indy is
cross-platform, any wrapper interface around WinInet would have to be
generic enough to allow for altenative implementations in other
platforms.
> I realize this would require some work to get redirects etc.
> working... But still...?
It would require a major re-write of Indy in general in order to
support what you are suggesting. Not just for TIdHTTP but throughout
all of Indy's conection-based components. There is no incentive for
Indy to do that over using the socket API directly like it currently
does.
Gambit
