Daniel Stenberg wrote:
> Troll. Get lost.
I'm not a troll - I'm not trying to induce a flame war.

I'm simply (over)reacting to your condescending tone. For which I am sorry.
I had no right to use such harsh words. And you had no right to use such a
tone.

I've expressed respect to all of you originally and expected respect in
response.

I'll try to rewrite my previous message:
---:<---
Yes I know what HEAD method is. I'm simply using word "head" to refer to a
collection of "headers". I'm not a native speaker, so I could be wrong.

sepheaders.c does a different thing. Besides, it does so incorrectly: it
returns nmemb, instead of expected (as documented) nmemb*size.

After experimenting a little with both sepheaders.c and my demo code I now
seem to understand what's happening. It seems that if no custom header
writing function is specified with CURLOPT_HEADERFUNCTION, the data writing
function is used in its place, either default or specified with
CURLOPT_WRITEFUNCTION. So in my demo code the headers got fed to my
discarding function.

However, the described behaviour is not documented and that's why I was
puzzled by it. I could fix the documentation, though. Where could I send
patches?
--->:---

And below is what I have expected to be in your original reply:
---:<---
If you don't supply a header writing function with CURLOPT_HEADERFUNCTION,
the data writing function is used instead (either default one or custom one,
supplied with CURLOPT_WRITEFUNCTION).
--->:---

Sincerely,
Nick
Received on 2008-04-03