Commit d5baaf77 authored by Daniel Stenberg's avatar Daniel Stenberg
Browse files

The big POST to HTTPS is probably not a bug.

The CONNECT problem is now bug #25 planned to get fixed in next release.
parent 2a94387f
Loading
Loading
Loading
Loading
+3 −2
Original line number Diff line number Diff line
@@ -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 - 
+6 −0
Original line number Diff line number Diff line
@@ -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: