X-Git-Url: https://git.m6w6.name/?p=m6w6%2Fext-http;a=blobdiff_plain;f=KnownIssues.txt;h=d54a683521503571adc3836aa37e8516e268abf0;hp=c0cb89f86fdc9062e43f303ef9238f6b6f13d5ff;hb=4e2ecc5ed84649ce20fd1f11319626e0b1befa0a;hpb=d83edb65a0097de2d5baa1a9fd9dbcebed34cc79 diff --git a/KnownIssues.txt b/KnownIssues.txt index c0cb89f..d54a683 100644 --- a/KnownIssues.txt +++ b/KnownIssues.txt @@ -2,12 +2,35 @@ Known Issues ============ $Id$ -HttpResponse class is only available for PHP >= 5.1 +HttpResponse (only in PHP-5.1+): + HttpResponse::getHeader() does not work in Apache2 with a +PHP version lower than 5.1.3 (as mod_php). -Not all places where files are handled check for open_basedir and/or safe_mode. +Windows: + If you keep getting "SSL connect error" when trying to issue +requests, try another (newer) libeay32.dll/ssleay32.dll pair. +Deflate/Inflate: + http_inflate() resp. the HttpInflateStream should be able to inflate +any compressed data (gzip, deflate AKA zlib and raw deflate). However, +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. + http_deflate() resp. the HttpDeflateStream should be able to +generate any compressed data (gzip, deflate AKA zlib and raw deflate); +just use the flag for the data format you want to generate: +HTTP_DEFLATE_TYPE_GZIP, HTTP_DEFLATE_TYPE_ZLIB or HTTP_DEFLATE_TYPE_RAW. + Using an encoding stream filter on a stream you read from, will +not work as expected in a PHP version lower than 5.1.3. Internals: - - the request bodies created in http_request_pool_attach() are not - destroyed in http_request_pool_detach(); may be a memory problem - in long running scripts \ No newline at end of file + - 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(). + + - our http_urlencode_hash() only handles arrays and does not + differentiate between prefixes for numeric or string keys. + + - check all places where hash table entries are created if + the keys are properly NUL terminated (prior 1.0!)