> I've now pushed commit 9dd85bced56 which fixes the problem. It now clearly
> closes the connection in request 2 and request 3 creates a new connection.
>

Thanks! Thinking further, is there enough information available to recognize the connection as not being "dirty" in this case and actually leave it open? It appears that closing the connection in case when no data was sent out is somewhat pessimistic and wastes a perfectly good connection.
                                               
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-10-02