Libcurl is doing connection caching. When easy handle is cleaned up, if the handle was previously used by the curl_multi_api, the connection remains open un the curl multi handle is cleaned up. Some protocols are sending content like the FTP one, and libcurl try to use the WRITEFUNCTION or the HEADERFUNCTION. Since structures used in those callback are freed, we need to use an other callback to which avoid segfaults. Libcurl commit d021f2e8a00 fix this issue and should be part of 7.28.2
Since curl multi is used, it sometime happen that the resource is freed before the curl multi really execute the query. The patch will store the headers slist in the curlstream handle and free it only when the stream will be closed
In fpm-log, possible buffer overflow. Check for length is done at the beginning of the loop, so is not done when overflow occurs on the last loop (len = 1024 or 1025). (ack from fat). This issue where found from by static code analysis tool and, so, I can't provide any reproducer.
… from value Restore the old behavior but keep bug 51094 fixed
…ng.encoding_translation = On)
Fix by (daniel dot stelter-gliese at innogames dot de). No test is supplied because the issue addresses the new feature of the Windows Server 2012 and would need a very specific filesystem setup.
…() causes memleak) Simply change the expect parameter type, the valid of the resource will be checked in using time.
Unitialized values warnings seem to be everyday life when working with openssl. For more read http://www.openssl.org/support/faq.html#PROG13 So just fixing so the bug, no care about those warnings.