The big POST to HTTPS is probably not a bug.

The CONNECT problem is now bug #25 planned to get fixed in next release.

diff --git a/TODO-RELEASE b/TODO-RELEASE
index 86a70e929eccafc2f721418c711485c30d91af5a..50123f70504c0ac994cbf8df07af18af147ea247 100644 (file)
--- a/TODO-RELEASE
+++ b/TODO-RELEASE
@@ -3,9 +3,10 @@ Issues not sorted in any particular order.
 To get fixed in 7.14.1 (planned release: August 2005)
 ======================
 
-60 - CONNECT 407 responses that kills the connection
+To get fixed in 7.14.2 (planned release: October 2005)
+======================
 
-62 - The sending big POST data to HTTPS bug
+60 - CONNECT 407 responses that kills the connection
 
 63 - 
 

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index a8b29896dcd77df170616853a9c98dcbba02f747..d19fdf3afb408fb9ac8b2f184c41ffe221a7a709 100644 (file)
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -3,6 +3,12 @@ join in and help us correct one or more of these! Also be sure to check the
 changelog of the current development status, as one or more of these problems
 may have been fixed since this was written!
 
+25. When doing a CONNECT request with curl it doesn't properly handle if the
+  proxy closes the connection within the authentication "negotiation phase".
+  Like if you do HTTPS or similar over a proxy and you use perhaps
+  --proxy-anyauth. There's work in progress on this problem, and a recent
+  patch was posted here: http://curl.haxx.se/mail/lib-2005-08/0074.html
+
 24. Harshal Pradhan's Use-after-free with libcurl+ares. This probably occurs
   because there is a pending ares callback that gets called after the
   connection struct has been freed in libcurl: