https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412010-06-02T12:32:44Zlighty labsLighttpd - Bug #2213: (connections.c.1698) SSL (error): 5 -1 0 Success https://redmine.lighttpd.net/issues/2213?journal_id=69882010-06-02T12:32:44ZAnonymous
<ul></ul><p>I can confirm this. This topic might be related: <a class="external" href="http://redmine.lighttpd.net/boards/2/topics/2779">http://redmine.lighttpd.net/boards/2/topics/2779</a></p> Lighttpd - Bug #2213: (connections.c.1698) SSL (error): 5 -1 0 Success https://redmine.lighttpd.net/issues/2213?journal_id=70312010-06-14T15:08:47Zstbuehler
<ul><li><strong>Target version</strong> changed from <i>1.4.27</i> to <i>1.4.x</i></li></ul><p>Yes, I still think this isn't our fault.</p> Lighttpd - Bug #2213: (connections.c.1698) SSL (error): 5 -1 0 Success https://redmine.lighttpd.net/issues/2213?journal_id=70322010-06-14T15:09:33ZOlaf-van-der-Spek
<ul></ul><p>In that case a link to the OpenSSL bug report would be nice. ;)</p> Lighttpd - Bug #2213: (connections.c.1698) SSL (error): 5 -1 0 Success https://redmine.lighttpd.net/issues/2213?journal_id=71422010-08-01T12:12:34Zbadmotorfinger
<ul></ul><p>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.</p>
<ul>
<li><a href="http://www.pubbs.net/201003/openssl/25267-problems-with-sslshutdown-and-non-blocking-socket.html" class="external">Description of the change</a></li>
<li>Major discussion <a href="http://marc.info/?t=119109061500001&r=1&w=2" class="external">here</a> and <a href="http://marc.info/?t=115154004000001&r=1&w=2" class="external">here</a></li>
</ul>
<p>So you're probably not going to see an OpenSSL bug on this one - they consider it to be a fix.</p> Lighttpd - Bug #2213: (connections.c.1698) SSL (error): 5 -1 0 Success https://redmine.lighttpd.net/issues/2213?journal_id=71582010-08-05T22:42:12Zstbuehler
<ul><li><strong>Target version</strong> changed from <i>1.4.x</i> to <i>1.4.27</i></li><li><strong>Missing in 1.5.x</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>Let me repeat what happened if you get that error message:</p>
<blockquote>
<p>SSL_shutdown failed, SSL_get_error returned SSL_ERROR_SYSCALL, but errno == 0</p>
</blockquote>
<p>The things you linked describe that SSL_shutdown may fail with SSL_ERROR_WANT_{READ,WRITE} - but that is not happening here.</p>
<p>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.</p> Lighttpd - Bug #2213: (connections.c.1698) SSL (error): 5 -1 0 Success https://redmine.lighttpd.net/issues/2213?journal_id=71592010-08-05T22:45:03Zstbuehler
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fixed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset r2749.</p>