shinrich edited a comment on pull request #7134: URL: https://github.com/apache/trafficserver/pull/7134#issuecomment-680104630
Yes, this logic has been present since the code was placed into gihub in 2009. I would assume that the timeout for the tunneling logic has never really worked appropriately either. The default value of proxy.config.net.default_inactivity_timeout is quite high 86400, so it normally wouldn't cause a conflict as long as at least one of the netVC retains a valid timeout. We somewhat recently started running with proxy.config.net.default_inactivity_timeout set to 500. But stepping back, why do we do this clearing of the timeout when a netvc is both read and write disabled? Is this something that used to make sense but does no longer? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
