Have you re-built your test application with the new .lib file?

Your e-mail got me thinking... There doesn't seem to be a .DEF file to
force functions to stay in the same place in the lookup table.

It looks like when you added SSL and compression, some of the functions
got re-arranged in the function lookup table.

I would take the newly created .lib file, replace the one your test
program is using and then do a build all on the test program.

I'd like to know how it works for you.

Brad Bruce

-----------------------------------------------------
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced
-----------------------------------------------------
 
-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Rathi, Dinesh
Sent: Tuesday, December 13, 2005 12:38 AM
To: libcurl development
Subject: RE: Issue with HTTP Post with Authentication - curl 7.12.2

I tried upgrading to 7.15.1 version and trying to run a testapp on
windows. I built libcurl using the curllib.dsw in lib folder. I switched
on SSL and compression and gave appropriate paths for zlib and openssl.
I am getting some weird errors while trying to run a simple test
application, when I call curl_global_init it actually calls curl_getdate
function and curl_easy_setopt gets mapped to curl_easy_perform.
Something has gone wrong when the dll built and when the exe built.
Something wrong with the API ordinal numbers, either my exe is taking it
from wrong place or libcurl.dll is generating it wrong. Anyone faced
similar issue, any known resolution?

Thanks
Dinesh

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Dan Fandrich
Sent: Monday, December 12, 2005 10:39 PM
To: curl-library_at_cool.haxx.se
Subject: Re: Issue with HTTP Post with Authentication - curl 7.12.2

On Mon, Dec 12, 2005 at 08:57:50PM +0530, Rathi, Dinesh wrote:
> Hi
>
> I am using curl library version 7.12.2 and trying to make
Web
> Service calls over HTTP using libcurl (i.e. HTTP Post requests). My
web service
> requires authentication so I set appropriate options, however for some
reason
> curl does not send Post request directly, it first tries to send a
Head request
> which fails since server does not support head requests. I tried to
look into
> the code and found that in Curl_http method (file http.c) we have
following
> piece of code, which makes the Head request before the post. I
commented this
> logic and things worked fine, now I am not sure what is the
side-effect of
> this, does anyone has more information?

This behaviour was changed in version 7.12.3; to wit:

- Made HTTP PUT and POST requests no longer use HEAD when doing
multi-pass
  auth negotiation (NTLM, Digest and Negotiate), but instead use the
request
  keyword "properly". Details in lib/README.httpauth. This also
introduces
  CURLOPT_IOCTLFUNCTION and CURLOPT_IOCTLDATA, to be used by apps that
use the
  "any" auth alternative as then libcurl may need to send the PUT/POST
data
  more than once and thus may need to ask the app to "rewind" the read
data
  stream to start.

There have been other POST fixes since then, so try upgrading to 7.15.1.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address
service
          Let webmasters know that your web site has moved
NOTICE: This e-mail and any attachment may contain confidential and/or legally privileged information. If you are not the intended recipient, you must not review, retransmit, print, copy, use or disseminate it. Please immediately notify us by return e-mail and delete it along with any attachment and do not retain a copy. If this e-mail contains a forwarded e-mail or is a reply to a prior e-mail, the contents may not have been produced by the sender and therefore we are not responsible for its contents.
This notice is automatically appended to each e-mail. It is the recipient's responsibility to take measures to ensure that this e-mail is virus free, and no responsibility is accepted by us for any loss or damage arising in any way from its use.