Lighttpd

well, async connecting is a little bit more difficult than what is used in mod_fastcgi.

• http://www.cyberconf.org/~cynbe/ref/nonblocking-connects.html
• http://cgit.lighttpd.net/lighttpd/lighttpd2/tree/src/common/memcached.c#n262

any chance of this patch making its way into lighttpd source tree? we been running it on a number of heavily loaded lighttpd servers on freebsd here at WhatsApp without any issues.

The question is: can it happen that sendfile gets ENOTCONN as in "and won't be connected ever"? you just assume ENOTCONN means "not yet connected".

Is the problem in this ticket still reproducible in FreeBSD 10?

mod_fastcgi is checking connect()ing socket for writability (POLLOUT) prior to attempting to write to socket. When detected as writable, mod_fastcgi checks getsockopt SO_ERROR to check that there was no socket error. This is an idiom I see quite often. Is there a different way to detect a connected socket on FreeBSD 8? The FreeBSD manpages suggest that what mod_fastcgi is doing is the right way to detect asynchronous connect has completed (or failed).

From FreeBSD man page for 'connect'
https://www.freebsd.org/cgi/man.cgi?query=connect&sektion=2&apropos=0&manpath=FreeBSD+10.2-RELEASE

     [EINPROGRESS]    The socket is non-blocking and the connection cannot
            be completed immediately.  It is possible to select(2)
            for completion by selecting the    socket for writing.

     SO_ERROR returns any pending error    on the socket and clears the error
     status.  It may be    used to    check for asynchronous errors on connected
     datagram sockets or for other asynchronous    errors.

Please close ticket: Missing Feedback.

If this is still a problem, please reopen ticket and provide new details. Thank you.