[jrgv]

what if your output is more than 2000 bytes?

The announcement says that "curl will inspect the beginning of each download", and I think that comparison just turns off the check after at least 2000 bytes have already been output (see a few lines below the change you quoted, where outs->bytes is incremented by the amount of bytes that were output).

what if your output is binary but doesn’t contain a byte 0?

I guess curl will incorrectly recognize the binary as text.

what if your output is a normal UTF-8 string but contains a byte 0?

I guess curl will incorrectly recognize the text as binary, and you can use `-o -` to override that and output to the terminal anyway.

[baby]

> I guess curl will incorrectly recognize the binary as text.

This doesn't sound like a really good test.

[raimue]

Looking for a NUL byte is the standard test that is also widely used by other tools such as grep or diff.

[baby]

Interesting, I'm going to try to implement that in my file parser.