On Sat, 6 Jun 2009, Aaron Oneal wrote: Please don't top-post, it makes it very hard to follow the thread.
Thanks, Daniel. I'm not aware of an easy way for the caller who doesn't have context of these other requests occurring to separate out the headers from the different responses, so I appreciate the consideration of an option to make this easier for apps to get at just the ones from the final response.
If you get a http status line you know it is the first line of a set of response-headers. That should be pretty easy to detect.
It would be great too if the docs could be updated to reflect that the current option returns headers from the multiple responses which occur during auth negotiation and not just the final response. I believe these changes would make it easier to use the library. Thanks.
Do you have any suggested changes/wording we could use? Would you look/expect this info to be (better) documented in the CURLOPT_HEADERFUNCTION description?
-- / daniel.haxx.se
