Thanks for bearing with me. I actually got the problem resolved yesterday.
I tried setting up
the CULROPTs as following:
...
    curl_easy_setopt(curl, CURLOPT_HEADER, 1);
    curl_easy_setopt(curl, CURLOPT_NOPROGRESS, 1);
    curl_easy_setopt(curl, CURLOPT_TRANSFERTEXT, 1);

    curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0);
    curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0);

    curl_easy_setopt(curl, CURLOPT_ERRORBUFFER, error);
...

And it works!! Thanks again for all the advices.

Best regards,
Iris

================================
On Wed, 13 Oct 2004, Iris Jing wrote:

>I still have one concern regarding user-agent. As Linus suggest, I can use
>curl_easy_setopt(curl, CURLOPT_USERAGENT,"bla bla") to set up the
>user-agent
>before I send out the request, but my problem is: what should I put in "bla
>bla".

Yes, that is your problem.

>Is there any way to figure out what kind of header the https server
>requires?

Yes, by looking in the source code they use or by asking the admins of the
site.

>I guess I have to make the remote server satisfied with the header I sent
>before it would allow me to get the target file...

Since the curl command line tool worked, a first shot could be to clone its
user-agent and see if it works.

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee®
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
Received on 2004-10-14