1

This has already been discussed several times, but this time I'm here to ask you because it's the same case.

First of all, the point of the problem is that when using the Get() function of TIdHTTP on an HTTPS web page, a message appears that the SSL library cannot be loaded.

So I added TIdSSLIOHandlerSocketOpenSSL to TIdHTTP::IOHandler, changed the TIdHTTP::HandleRedirects property to true, moved the libeay32.dll and ssleay32.dll files to the location of the executable file, and it worked normally in C++Builder Berlin.

However, in C++Builder 2007, even if I set it up with the same environment and Get() code, the "Could Not Load SSL Library" error appears.

If anyone has experienced similar problems, can you please give me your solution?

Improve this question
9
  • This sounds like something you should take up with the vendor, not stackoverflow. Commented Dec 7, 2021 at 9:00
  • @Botje Why? The question is obviously related to programming. He has written a code, and when he runs it an error appears. Commented Dec 7, 2021 at 11:32
  • stackoverflow.com/questions/50742852/issue-related-to-ssl-dll Commented Dec 7, 2021 at 11:35
  • @vll the problem was solved on a compiler version that is "only" five years old. C++ builder 2007 is 14 years old. Commented Dec 7, 2021 at 11:55
  • @Valtur "This has already been discussed several times, but this time I'm here to ask you because it's the same case" - then you really shouldn't be bringing this up again, as this topic has already been discussed in great detail many times before. In any case, are you using the version of Indy that shipped with CB2007? Have you tried upgrading to the latest Indy version yet? What version of the 2 DLLs are you using? What does Indy's WhichFailedToLoad() and OpenSSLVersion() functions report when the error occurs? Commented Dec 7, 2021 at 18:04

1 Answer 1

Reset to default
2

In comments, you mention that Indy's WhichFailedToLoad() function is reporting various ..._indy functions are missing in the OpenSSL DLLs. The fact that Indy is looking for those functions means you are using Indy v8 or v9, not v10. You can verify that by looking at the gsIdVersion global variable in the IdGlobal unit.

Indy v8 and v9 require custom-built OpenSSL 0.9.6 DLLs. At the time, Indy needed access to various OpenSSL internals that OpenSSL did not expose public access to yet (that was rectified in later OpenSSL versions), so Indy needed to add some custom functions to the DLLs. You can get those DLLs from the Archive folder of Indy's OpenSSL-Binaries repository.

However, Indy v8 and v9 are OLD and no longer supported. They DO NOT support OpenSSL 1.0.x and later versions. You will have to upgrade to Indy v10, which uses standard OpenSSL DLLs, and officially supports up to OpenSSL 1.0.2u (support for OpenSSL 1.1.x is work in progress, but you can try it if you need to use OpenSSL 1.1.x, such as for TLS 1.3).

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.