Project

General

Profile

Actions

Bug #5226

closed

/sockopen read timeout is too low

Added by westor (GR) about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Scripting
Target version:
Start date:
02/10/2021
Due date:
% Done:

0%

Estimated time:
Operative System:
All
Regression:
No

Description

Hello,

I was trying to create a code, when i saw that AdiIRC drops the TLS connection after some seconds (probably between 300-500) as it should not, also not any $sockerr identifier triggers.

$version || $beta || $osversion || $dotnet
4.0 || 20210124 || Windows 10 Enterprise (Version 10.0 2009  Build 19042.746) || v4.0.30319

Rawlog Debug Message :

SockClose: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Reproduce Code :

alias adi_bug {
  sockclose bug

  sockopen -e bug irc.chathub.org 6697
}

ON *:SOCKOPEN:bug: {
  if ($sockerr) { echo 4 Error 1 ! -> $sock($sockname).wsmsg | return }

  sockwrite -nt $sockname NICK adi_bug
  sockwrite -nt $sockname USER ident 0 * :gecos
}

ON *:SOCKREAD:bug: {
  if ($sockerr) { echo 4 Error 2 ! -> $sock($sockname).wsmsg | return }

  var %r
  sockread %r

  ;ping pong!
  if ($gettok(%r,1,32) == PING) { sockwrite -nt $sockname PONG : $+ $remove($gettok(%r,2-,32),:) }
}

- Thanks!

Actions #1

Updated by Per Amundsen about 3 years ago

  • Subject changed from AdiIRC stop responding when using a TLS socket connection to /sockopen read timeout is too low
  • Status changed from New to Resolved
Actions #2

Updated by Per Amundsen about 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF