On Wed, 29 Jan 2003, Jörg Müller-Tolk wrote:

> Callbacks set with option CURLOPT_HEADERFUNCTION won't be called in case of
> proxy-authentification, hostname resolve-problems, permission denied, etc.
> - is this correct? If yes, is it because doing it different will cause
> problems?

The callback is called on each header libcurl receives. If it aborts before
any headers are received, then no, it won't call the callback. If the
cancelation is done after one or more headers have arrived, then the callback
will be called.

It's as simple as that!

> I am very busy right now, but if I have some spare time I am interested in
> extending curl to support ugly bad proprietary behated NTLM proxy
> authentification. I have already opened a developer support call at
> microsoft wich is frozen right now. My first steps in this direction would
> be easier if I can use a callback on headers tags during proxy
> communications - I suppose.

Let me know what I (or others) can do to help.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com