Bug #2213
closed(connections.c.1698) SSL (error): 5 -1 0 Success
Description
My error.log is filled with lines like this. Doesn't look right...
Updated by Anonymous over 14 years ago
I can confirm this. This topic might be related: http://redmine.lighttpd.net/boards/2/topics/2779
Updated by stbuehler over 14 years ago
- Target version changed from 1.4.27 to 1.4.x
Yes, I still think this isn't our fault.
Updated by Olaf-van-der-Spek over 14 years ago
In that case a link to the OpenSSL bug report would be nice. ;)
Updated by badmotorfinger over 14 years ago
It appears to be due to a change in OpenSSL 0.9.8m's SSL_shutdown call in non-blocking environments. Not sure if the damage is purely cosmetic or causing other misbehavior on socket shutdown.
- Description of the change
- Major discussion here and here
So you're probably not going to see an OpenSSL bug on this one - they consider it to be a fix.
Updated by stbuehler over 14 years ago
- Target version changed from 1.4.x to 1.4.27
- Missing in 1.5.x changed from No to Yes
Let me repeat what happened if you get that error message:
SSL_shutdown failed, SSL_get_error returned SSL_ERROR_SYSCALL, but errno == 0
The things you linked describe that SSL_shutdown may fail with SSL_ERROR_WANT_{READ,WRITE} - but that is not happening here.
So i still consider this an openssl bug. As i don't care about stupid ssl shutdown errors (we are in the lighty connection error state too anyway), i will just silence the error now.
Updated by stbuehler over 14 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset r2749.
Also available in: Atom