Shmulik Regev found an (albeit rare) case where the proxy CONNECT operation

could in fact get stuck in an endless loop.

1 files changed, 6 insertions, 0 deletions

diff --git a/lib/url.c b/lib/url.c
index 24cbaaf89..a12d94d63 100644
--- a/lib/url.c
+++ b/lib/url.c
@@ -4071,6 +4071,12 @@ static CURLcode SetupConnection(struct connectdata *conn,
   }
   *protocol_done = FALSE; /* default to not done */
 
+  /* set proxy_connect_closed to false unconditionally already here since it
+     is used strictly to provide extra information to a parent function in the
+     case of proxy CONNECT failures and we must make sure we don't have it
+     lingering set from a previous invoke */
+  conn->bits.proxy_connect_closed = FALSE;
+
   /*************************************************************
    * Set user-agent for HTTP
    *************************************************************/