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?

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.

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
Received on 2003-01-29