-
-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled SB-INT:CLOSED-STREAM-ERROR using SSL + Hunchentoot #127
Comments
error output log:
|
This issue is moot for me. I continue to get the error but my site works since I changed the configuration of sb-daemon to allow for errors. Also I am now planning to switch to nginx as a reverse proxy to handle ssl. |
I got nginx handling ssl on port 443 and as a proxy for clack/hunchentoot on port 8080. With the added benefit that nginx will redirect http://mysite.com to https://mysite.com. So for me this is really not an important issue. |
This is affecting me, even without SSL. |
Method binds hunchentoot:*catch-errors-p* to NIL, so hunchentoot tries to invoke a debugger if a condition comes to it. Error condition wasn't handled by clack if it happened in handle-response, because handler-case was wrapped around funcall, not the whole expression. HANDLE-RESPONSE might have raisen an exception from SSL library (and other communication methods) for instance when peer has closed the connection - that lead to uncought closed stream error condition. Fixes fukamachi#127.
I get this error while using port 443 and ssl. :debug is true.
This occurs a few minutes after getting home page and then idling. It does not occur with port 80 and no ssl.
It is evoked in caveman by
The text was updated successfully, but these errors were encountered: