Branch :
- branch -
master
- tag -
release-1.1b
release-1.4.0-beta
release-1.4.1-beta
release-1.4.10-stable
release-1.4.11-stable
release-1.4.12-stable
release-1.4.13-stable
release-1.4.14-stable
release-1.4.14b-stable
release-1.4.15-stable
release-1.4.2-rc
release-1.4.3-stable
release-1.4.4-stable
release-1.4.5-stable
release-1.4.6
release-1.4.7-stable
release-1.4.8-stable
release-1.4.9-stable
release-2.0.1-alpha
release-2.0.10-stable
release-2.0.11-stable
release-2.0.12-stable
release-2.0.13-stable
release-2.0.14-stable
release-2.0.15-stable
release-2.0.16-stable
release-2.0.17-stable
release-2.0.18-stable
release-2.0.19-stable
release-2.0.20-stable
release-2.0.21-stable
release-2.0.22-stable
release-2.0.23-beta
release-2.0.3-alpha
release-2.0.4-alpha
release-2.0.5-beta
release-2.0.6-rc
release-2.0.7-rc
release-2.0.8-rc
release-2.0.9-rc
release-2.1.1-alpha
release-2.1.10-stable
release-2.1.11-stable
release-2.1.12-stable
release-2.1.2-alpha
release-2.1.3-alpha
release-2.1.4-alpha
release-2.1.5-beta
release-2.1.6-beta
release-2.1.7-rc
release-2.1.8-stable
release-2.1.9-beta
release-2.2.1-alpha
Log
Author
Commit
Date
CI
Message
cf749e22 2009-11-18 21:16:53
Add a temporary workaround for an ssl bug found on FreeBSD.
Basically, we only want to report the 'connected' event because of
the socket connect() finishing when we have an actual socket
bufferevent; on an SSL bufferevent, 'connected' means 'SSL
connection finished.'
This isn't FreeBSD's fault: it just has a connect() that tends to
succeed pretty early.
svn:r1548
