Re: HTTPS using Indy

>The client should need nothing else except a route to connect to the
>server. Usually this will be on port 443.

Great! One problem less.

>I assume you have the SSL dll's (libeay32.dll and ssleay32.dll) for
>indy to use?

I have put these dll's in the application directory, but when I call
the TIdHTTP get method to a "https" URL, I receive the following error
message: "Could not load SSL Library".

I have been googling for this, but all the documents I find tell that
it suffices to have the dll's. Well, it is not my case...

.

Relevant Pages

  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: RealVNC
    ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN routing - single NIC - SOLVED
    ... What should happen is that the server ... acts as a proxy for the remote client. ... idea is to put the remotes in their own IP subnet and route this subnet ... Nothing is configured in RAS Admin - No policy and no Static Route. ...
    (microsoft.public.windows.server.networking)