back to dev

[m6w6/ext-http] / KnownIssues.txt

diff --git a/KnownIssues.txt b/KnownIssues.txt
index 94a0a94dcdedae8b96c9ae95c7fb27a54dcc564c..4c2ad80b6025a49554ce2b2c54e6b02063385c26 100644 (file)
--- a/KnownIssues.txt
+++ b/KnownIssues.txt
@@ -1,6 +1,5 @@
 Known Issues
 ============
-$Id: KnownIssues.txt 292753 2009-12-29 12:30:43Z mike $
 
 Windows:
        If you keep getting "SSL connect error" when trying to issue 
@@ -16,14 +15,11 @@ Internals:
                as libcurl saves the cookies to the file on curl_easy_destroy(),
                cookies are not saved 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
+                               * run PHP with raphf.persistent_handles.limit = 0
+                               * call raphf\persistent_handles_clean() every request
+                               * call $client->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, so using
-                       HttpRequestDatashare with cookies enabled is probably the
-                       best thing to do.
        HTTP and Proxy authentication information (username/password) can not be
                unset with NULL prior libcurl v7.19.6 and separate options for setting
                username and password--which work--are only available since v7.19.6.