> On Dec 15, 2021, at 12:49 PM, Ross Finlayson <finlay...@live555.com> wrote: > >> It seemed to me from the comments, and from the man page of connect(), that >> on a nonblocking socket after calling connect() and select(), one is advised >> to check SO_ERROR. >> In case of HTTP tunneling, the connection handler is entered twice: first >> for the GET connection, and later for the POST connection. >> The second time it happens when select() indicates that fOutputSocketNum >> became ready, and it is not about sent or received data, it is about the >> connect() call. >> Without the patch, we call the connection handler after the POST connection >> is opened on fOutputSocketNum, but we still check getsockopt() on >> fInputSocketNum. > > OK, thanks for the clarification. I’ll look into this.
FYI, your proposed patch here was correct. I have just released a new version (2021.12.18) of the code that includes this. Thanks again. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
