- When downloading compressed content over HTTP and the app as asked libcurl to automatically uncompress it with the CURLOPT_ENCODING option, libcurl could wrongly provide the callback with more data than what the maximum documented amount. An application could thus get tricked into badness if the maximum limit was trusted to be enforced by libcurl itself (as it is documented). This is further detailed and explained in the libcurl security advisory 20100209 at http://curl.haxx.se/docs/adv_20100209.html
Modified test case 557 to additionally verify libcurl's internal curl_m*printf() functions formatting functionality when handling signed and unsigned shorts.
cookies with same path length might get sorted in different order when using different qsort implementations. In order to make this test give same results on different systems, paths now have different lengths.