X-Git-Url: https://git.m6w6.name/?p=m6w6%2Fext-http;a=blobdiff_plain;f=KnownIssues.txt;h=2453f2774c4acbb25cacdc0cc5c4a3945d3a0109;hp=87c6db416c8b52b42497a30409eca241031a416b;hb=b1ace11a9604ffcc496d32827aa66a2ba99db5ff;hpb=f2f3d343bf1e1c1270eb6db5487ff0bbf086b900

diff --git a/KnownIssues.txt b/KnownIssues.txt
index 87c6db4..2453f27 100644
--- a/KnownIssues.txt
+++ b/KnownIssues.txt
@@ -2,12 +2,30 @@ Known Issues
 ============
 $Id$
 
-HttpResponse class is only available for PHP >= 5.1
+PHP < 5.1.3:
+	HttpResponse::getHeader() does not work with Apache2 SAPIs.
+	Using an encoding stream filter on a stream you read from doesn't work.
 
-HttpResponse::guessContentType() is not available on Windows at the time this
-was written, unless you compile PHP or ext/http yourself[1]. Additionally
-you'll need to fix the magic.mime file that's shipped with PHP by executing
-`sed -e "s/\t!/\\\!/" magic.mime > magic.good` and then of course use the new 
-magic file.
+Windows:
+	If you keep getting "SSL connect error" when trying to issue 
+		requests, try another (newer) libeay32.dll/ssleay32.dll pair.
 
-[1] Fetch http://dev.iworks.at/PATCHES/fileinfo/fileinfo-win32build.zip (84k)
+Internals:
+	Our http_urlencode_hash() does not differentiate between prefixes
+		for numeric or string keys.
+	Inflating raw deflated data causes a re-initialization of the inflate
+		stream where the corresponding window bits are modified to tell libz
+		to not check for zlib header bytes.  This is not preventable AFAICS.
+	LFS dependant parts of libcurl are left out because of off_t,
+		respectively off64_t confusion.
+	Persistent handles and "cookiestore" request option do interfere,
+		as libcurl safes the cookies to the file on curl_easy_destroy(),
+		cookies are not safed until the CURL handle will be recycled.
+			Thus one would either need to
+				* run PHP with http.persistent.handles.limit = 0
+				* call http_persistent_handles_clean() every request
+				* call $HttpRequest->flushCookies(), which is available
+				  since libcurl v7.17.1 and does not work with the
+				  procedural API
+			Anyway, none of these options is really perfect.
+