🚀 go-pugleaf

"Blake Young" <blakeyoung@mail.utexas.edu> wrote in message
news:42e00af1$1@newsgroups.borland.com...

> Despite the fact that it has a secure URL (hence "https"), a
> username and password is NOT needed to download the file.

Perhaps not, but an SSL negotiation is still required.

> the response to the GET command is a 302 error, saying that
> the file has been moved.

As it should be.  See below.

> I believe the problem is that I cannot get either component to
> connect to the HTTPS location...

Yes, you can.  TIdHTTP has support for HTTPS URLs.

> they only try the HTTP location.

That may be the case for your TClientSocket code, but that is not the case
with TIdHTTP.

> Here is my code:

Your TClientSocket code is not HTTPS-aware at all.

>        ClientSocket1->Host = "webspace.utexas.edu";
>        ClientSocket1->Port = 80;

You are not accessing "https://webspace.utexas.edu" at all.  You are
accessing "http://webspace.utexas.edu" instead.  HTTPS runs on port 443, not
port 80.  That makes a big difference.

> The response I get from ReceiveText() should just be the single line
> of text that makes up the "version.txt" file

No, it should not, because you are not accessing the HTTPS URL at all.  You
can even see in the response from "http://webspace.utexas.edu" (port 80)
that you are being redirected to "https://webspace.utexas.edu" (port 443)
instead.

> The only thing I can think of is that maybe it's originally trying to go
to
> the non-secured URL first (i.e. http://webspace.utexas.edu/...) instead
> of the secure https location.

That is exactly what your TClientSocket code is doing.

> If this is indeed the problem, how can I use the component (either
> TClientSocket or TIdHTTP) to access the https URL?

For TClientSocket, you need to change the Port that is used.

For TIdHTTP, it handles HTTPS automatically, so you do not need to do
anything for it.


Gambit