fix(connectionhandler): Delay socket termination in TLS session resumption handling to allow proper alert processing
This commit is contained in:
		| @@ -3,6 +3,6 @@ | ||||
|  */ | ||||
| export const commitinfo = { | ||||
|   name: '@push.rocks/smartproxy', | ||||
|   version: '4.1.14', | ||||
|   version: '4.1.15', | ||||
|   description: 'A powerful proxy package that effectively handles high traffic, with features such as SSL/TLS support, port proxying, WebSocket handling, dynamic routing with authentication options, and automatic ACME certificate management.' | ||||
| } | ||||
|   | ||||
| @@ -625,10 +625,10 @@ export class ConnectionHandler { | ||||
|               const finishConnection = () => { | ||||
|                 // Give Chrome more time to process the alert before closing | ||||
|                 // We won't call destroy() at all - just end() and let the socket close naturally | ||||
|                 socket.end(); | ||||
|                  | ||||
|                 // Log the cleanup but wait for natural closure | ||||
|                 setTimeout(() => { | ||||
|                   socket.end(); | ||||
|                   this.connectionManager.cleanupConnection(record, 'session_ticket_blocked_no_sni'); | ||||
|                 }, 5000); // Longer delay to let socket cleanup happen naturally | ||||
|               }; | ||||
|   | ||||
		Reference in New Issue
	
	Block a user