- using Accept-Encoding header instead of CURLOPT_ENCODING avoids issues with curl...

[m6w6/ext-http] / KnownIssues.txt

diff --git a/KnownIssues.txt b/KnownIssues.txt
index f4e945008aa2a6393f40225e73df0a4e180b1c2d..adfcfe3464083657f8b31ac903379010b841309a 100644 (file)
--- a/KnownIssues.txt
+++ b/KnownIssues.txt
@@ -6,19 +6,11 @@ HttpResponse class is only available for PHP >= 5.1
 
 Not all places where files are handled check for open_basedir and/or safe_mode.
 
-Throttling with the FastCGI SAPI may behave unexpected, because libfcgi seems
-not to practically flush its buffers when calling sapi_flush().
-See also http://bugs.php.net/bug.php?id=34429
-
 If you keep getting "SSL connect error" when trying to issue requests on
 Windows, try another (newer) libeay32.dll/ssleay32.dll pair.
 
-Inflating compressed HttpRequest responses happens twice if libcurl
-was built with zlib support.
-
 Internals:
-       -       the request bodies created in http_request_pool_attach() are not 
-               destroyed in http_request_pool_detach() but on reset; 
-               may be a memory problem in long running scripts which reuse one
-               request pool several times
-
+       -       there's a memleak with sizeof(zval) for each thrown exception, 
+               which ends up in HttpRequestPoolExcepiont::$exceptionStack, in 
+               HttpRequestPool::__construct(); it doesn't happen with wrapped
+               exceptions in HttpRequestPool::send().