Re: [Twisted-Python] HTTP Agent persistent connections not closed for some HTTPS sites

> It looks like when connected to some HTTPS servers, the TLS connection is not successfully closed. > But with Office365 sharepoint.com sites the TLS shutdown is not completed. > Has anyone else observed this behaviour ? I observed something simillar a while ago, there was bug report created

[Twisted-Python] twistedmatrix.com TLS certificate

twistedmatrix.com's current certificate is issued by StartCom Certification Authority; for certificates issued by this CA prior to 2016-09-21, the domain must be on a Chrome whitelist for it to be accepted. As of Chrome 58.0.3026.3 (canary/dev channel only, currently, but eventually this will

Re: [Twisted-Python] HTTP Agent persistent connections not closed for some HTTPS sites

> On Mar 5, 2017, at 6:25 AM, Tristan Seligmann wrote: > > I think this code should either call abortConnection directly, or set a timer > which will abort the connection after a little while if a clean shutdown from > loseConnection has not completed yet. I' >

Re: [Twisted-Python] HTTP Agent persistent connections not closed for some HTTPS sites

On Sun, 5 Mar 2017 at 15:36 Adi Roiban wrote: > I have observed this while running some end to end tests in which the > pool.closeCachedConnections() deferred was not called, even after a > generous amount of seconds :) > The code to abort an HTTP client connection is here:

[Twisted-Python] HTTP Agent persistent connections not closed for some HTTPS sites

Hi, It looks like when connected to some HTTPS servers, the TLS connection is not successfully closed. With sites like google.com, the connection is successfully closed. But with Office365 sharepoint.com sites the TLS shutdown is not completed. Has anyone else observed this behaviour ? I