On Thu, 24 Apr 2003, Dan Fandrich wrote:

> That's how it works now and how I suggest we leave it--setting NULL means
> not to send Accept-Encoding and to ignore a received Content-Encoding.
>
> My suggestion is to set CURLENCODE_ALL_SUPPORTED to "", i.e. an empty string.
> That would be replaced inside the library with the set of Accept-Encodings
> supported. I can't think of a reason anyone would want to send an
> Accept-Encoding: line with no argument, although it appears to be legal.

I think this makes sense.

> It's just a bit more work for the programmer who wants digested headers. I
> would be useful to have a function that returns all the headers in a struct
> curl_slist or some other preprocessed form. It's not something I need
> right now, but it's something that could be used to elegantly bloat libcurl
> if people think it's not big enough yet ;-)

Well, if anyone wants them in a list, then its easy to add a callback that
simply adds them to a list... :-)

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf