On Mon, 22 Aug 2011, Yang Tse wrote:

>> At times HEADERFUNCTION+HEADERDATA was set only to have only
>> HEADERDATA set in the subsequent loop which could cause a NULL
>> to get sent as userdata to 'header_callback' which wasn't made
>> to handle that.
>>
>> Now HEADERFUNCTION is explicitly set to NULL if it isn't set to the
>> callback.
>
> Shouldn't this take in account that there might exist cached data due to
> write being paused, or no longer paused but still with cached data, when the
> header write callback is reset on the fly, and somehow deal with it?

No. This setting of the HEADERFUNCTION option is only done between calls to
curl_easy_perform() so there will be nothing in particular cached that would
be ruined because of this.

(I realize this thread should've been on the curl-users list from the
beginning but since I didn't notice early enough I've just kept it here.)

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html