-
Notifications
You must be signed in to change notification settings - Fork 579
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
[dev.icinga.com #12493] API Remote crash via Google Chrome #4524
Comments
Updated by mfrosch on 2016-08-19 17:09:56 00:00 Can not reproduce the behavior with openssl s_client I think this might be connected to some keepalive handling of Chrome, and the line we see here in logs:
Could this be some HTTP/2 issue? |
Updated by mfrosch on 2016-08-19 17:33:28 00:00 This does not happen in a 2.4.10-1 test setup (Note: single node with API) |
Updated by mfrosch on 2016-08-19 17:41:10 00:00
Removing private, since not reproducible with released version. |
Updated by gbeutner on 2016-08-19 18:40:04 00:00
Applied in changeset b42bfc8. |
Updated by gbeutner on 2016-08-22 11:40:55 00:00
|
Updated by gbeutner on 2016-08-22 11:41:09 00:00
|
Updated by gbeutner on 2016-08-22 11:41:17 00:00
|
Updated by gbeutner on 2016-08-22 14:37:59 00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12493
Created by mfrosch on 2016-08-19 17:06:03 00:00
Assignee: gbeutner
Status: Resolved (closed on 2016-08-19 18:40:04 00:00)
Target Version: 2.5.0
Last Update: 2016-08-22 11:41:17 00:00 (in Redmine)
Private for now...
Icinga 2 crashes in HTTP library when accessed by Google Chrome
Crash report attached.
Still gathering Information.
The crash happens when you do the following steps in Chrome:
Attachments
Changesets
2016-08-19 18:36:27 00:00 by gbeutner b42bfc8
Relations:
The text was updated successfully, but these errors were encountered: