Websockets - 150 seconds to connect to the endpoint #10157
I did this
I am using the
I expected the following
I'd expect curl to routinely check the underlying socket until it becomes writable.
This might help in reproducing the bug
The text was updated successfully, but these errors were encountered:
@icing isn't this a bug? In this case, there's a socket filter and an SSL filter added, and when
In that function, the state is neither of the two checked for, so it returns blank. This, while the socket is not yet connected. Surely it calls the wrong getsock() here prematurely?
Since there are filters addded for both socket and SSL, the code previously checked the SSL sockets during connect when it *should* first check the socket layer until that has connected. Fixes #10157