- 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 8fa37c75e403221824f75bc2c3ced7dde7104e05..adfcfe3464083657f8b31ac903379010b841309a 100644 (file)
--- a/KnownIssues.txt
+++ b/KnownIssues.txt
@@ -2,31 +2,15 @@ Known Issues
 ============
 $Id$
 
-Issues I don't know how to solve yet are as follows:
+HttpResponse class is only available for PHP >= 5.1
 
-There are odd memory corruptions when HttpRequest objects
-are created with urls out of an array and attached to an
-HttpRequestPool object -- see HttpRequestPool_001.phpt
+Not all places where files are handled check for open_basedir and/or safe_mode.
 
-[Tue Jun 14 20:19:34 2005]  Script:  'tests/HttpRequestPool_001.php'
----------------------------------------
-/home/mike/dev/cvs/pecl/http/http_request_api.c(184) : Block 0x082919EF status:
-Beginning:      Overrun (magic=0x12F8DC00, expected=0x7312F8DC)
-      End:      Unknown
----------------------------------------
-[Tue Jun 14 20:19:34 2005]  Script:  'tests/HttpRequestPool_001.php'
----------------------------------------
-/home/mike/dev/cvs/pecl/http/http_request_api.c(184) : Block 0x08291BE7 status:
-Beginning:      Overrun (magic=0x12F8DC00, expected=0x7312F8DC)
-      End:      Unknown
----------------------------------------
-[Tue Jun 14 20:19:34 2005]  Script:  'tests/HttpRequestPool_001.php'
----------------------------------------
-/home/mike/dev/cvs/pecl/http/http_request_api.c(184) : Block 0x08291D3F status:
-Beginning:      Overrun (magic=0x12F8DC00, expected=0x7312F8DC)
-      End:      Unknown
----------------------------------------
-/home/mike/dev/cvs/pecl/http/http_request_api.c(156) :  Freeing 0x08291D68 (36 bytes), script=tests/HttpRequestPool_001.php
-Last leak repeated 2 times
-=== Total 3 memory leaks detected ===
+If you keep getting "SSL connect error" when trying to issue requests on
+Windows, try another (newer) libeay32.dll/ssleay32.dll pair.
 
+Internals:
+       -       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().