Daniel,

Sounds good.

The second method seems cleaner (for the s/w developer, no callbacks to
write) - just pass in a curl_slist of alternating strings & aliases, or
strings to be considered "HTTP 200 OK".

Please let me know how you want to proceed.
Cheers
Simon

On Monday, November 11, 2002, at 11:15 PM, Daniel Stenberg wrote:

> On Mon, 11 Nov 2002, ruffnex wrote:
>
>> Could you please expand on "a custom check"?
>> Apart from callbacks what else can the application supply to libcurl? Or
>> are you suggesting that I should just add some header parsing code to my
>> body callback function?...
>
> I was thinking perhaps we should introduce a way for the application to
> tell
> libcurl what kind of initial header that is OK. Either we add yet another
> callback, or perhaps we can allow a string to be passed in to be matched
> and
> if it matches the input is considered OK. Or whatever.
>
> --
> Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
>

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2002-11-11