Bug #4010
closed/sockopen -e SSL cannot connect on host in some cases
0%
Description
Hello,
There is a bug on /sockopen -e, i didn't saw that error in the past on adiirc but i've try to use that host and returns an error message, i know that you made an fix on /sockopen (i saw it in the changelog on Unreleased section for the next beta release) but i am not sure if your fix effecting this case too, also i've downloaded the latest build from your FTP and run that code that it should include your recent fix on /sockopen but the results were the same (but i am not sure if you including in your latest build on your FTP the recent fix on /sockopen that's why i reported).
Reproduce code:
Execute /test_sock
alias test_sock { sockopen -e test_sock pixxxels.cc 443 } ON *:SOCKOPEN:test_sock: { if ($sockerr) { echo 4 -s OPEN ERROR: $sock($sockname).wserr -> $sock($sockname).wsmsg | return } sockwrite -nt $sockname GET /image/kreg4u8bb/ HTTP/1.1 sockwrite -nt $sockname Host: $sock($sockname).addr sockwrite -nt $sockname Connection: Close sockwrite -nt $sockname $crlf } ON *:SOCKREAD:test_sock: { if ($sockerr) { echo 4 -s READ ERROR: $sock($sockname).wserr -> $sock($sockname).wsmsg | return } }
Error message (translated): OPEN ERROR: 1 -> A call to SSPI failed, check your local exception.
Rawlog (translated): -> 09/07/2018 06:29:05 - RunLoop: Unable to connect to 104.18.46.220:443 (A call to SSPI failed, check your local exception.. - The received message was not expected or was in the wrong format)
- Thanks!