On Tue, 14 Feb 2012, Vladimir Grishchenko wrote:
I understand this is not required and HTTP 1.0-style connections are rarely used today if ever, but is there a particular reason libcurl doesn't send the Connection: close header when CURLOPT_FORBID_REUSE option is in effect? One difference it would make is that connections will not go into the TIME_WAIT state on the client.
No, there's no reason and yes I agree that it should. I'd appreciate a patch! (Do note that there will be a bunch of test cases that will need attention)
-- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
