The message triggered earlier than intended and did not take the
transfer/content type into account.
Ref #21603
Reported-by: Joshua Rogers
Closes #21756
return CURLE_OK;
}
- if(Curl_cwriter_count(data, phase) + 1 >= MAX_ENCODE_STACK) {
- failf(data, "Reject response due to more than %d content encodings",
- MAX_ENCODE_STACK);
+ if(Curl_cwriter_count(data, phase) >= MAX_ENCODE_STACK) {
+ failf(data, "Reject response exceeding limit of %d %s encodings",
+ MAX_ENCODE_STACK,
+ is_transfer ? "transfer" : "content");
return CURLE_BAD_CONTENT_ENCODING;
}
61
</errorcode>
<stderr mode="text">
-curl: (61) Reject response due to more than 5 content encodings
+curl: (61) Reject response exceeding limit of 5 transfer encodings
</stderr>
</verify>
</testcase>
61
</errorcode>
<stderr mode="text">
-curl: (61) Reject response due to more than 5 content encodings
+curl: (61) Reject response exceeding limit of 5 transfer encodings
</stderr>
</verify>
</testcase>