From 4551e7ce49275da08e5fcf0ef46944b42de892fc Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 28 Jan 2005 22:14:48 +0000 Subject: KNOWN_BUGS #17 fixed. A DNS cache entry may not remain locked between two curl_easy_perform() invokes. It was previously unlocked at disconnect, which could mean that it remained locked between multiple transfers. The DNS cache may not live as long as the connection cache does, as they are separate. To deal with the lack of DNS (host address) data availability in re-used connections, libcurl now keeps a copy of the IP adress as a string, to be able to show it even on subsequent requests on the same connection. --- docs/KNOWN_BUGS | 13 ------------- 1 file changed, 13 deletions(-) (limited to 'docs') diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 48c589294..bfa9aec18 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -6,19 +6,6 @@ may have been fixed since this was written! 18. test case 57 has that should be but when corrected, the test case fails! -17. Memory badness: - 1. create a multi handle - 2. add an easy handle - 3. fetch a URL that is persistent (leaves the connection alive) - 4. remove the easy handle from the multi - 5. kill the multi handle - 6. create a multi handle - 7. add the same easy handle to the new multi handle - 8. fetch a URL from the same server as before (re-using the connection) - - Use valgrind to see the memory problems when libcurl assumes that the DNS - data lives as long as the connection - 16. FTP URLs passed to curl may contain NUL (0x00) in the RFC 1738 , , and components, encoded as "%00". The problem is that curl_unescape does not detect this, but instead returns a shortened C -- cgit v1.2.3