{"action":"closed","issue":{"url":"https://api.github.com/repos/warmcat/libwebsockets/issues/684","repository_url":"https://api.github.com/repos/warmcat/libwebsockets","labels_url":"https://api.github.com/repos/warmcat/libwebsockets/issues/684/labels{/name}","comments_url":"https://api.github.com/repos/warmcat/libwebsockets/issues/684/comments","events_url":"https://api.github.com/repos/warmcat/libwebsockets/issues/684/events","html_url":"https://github.com/warmcat/libwebsockets/issues/684","id":191227989,"number":684,"title":"Provide explicit callback for X.509 client errors","user":{"login":"smipi1","id":5098978,"avatar_url":"https://avatars.githubusercontent.com/u/5098978?v=3","gravatar_id":"","url":"https://api.github.com/users/smipi1","html_url":"https://github.com/smipi1","followers_url":"https://api.github.com/users/smipi1/followers","following_url":"https://api.github.com/users/smipi1/following{/other_user}","gists_url":"https://api.github.com/users/smipi1/gists{/gist_id}","starred_url":"https://api.github.com/users/smipi1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smipi1/subscriptions","organizations_url":"https://api.github.com/users/smipi1/orgs","repos_url":"https://api.github.com/users/smipi1/repos","events_url":"https://api.github.com/users/smipi1/events{/privacy}","received_events_url":"https://api.github.com/users/smipi1/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-11-23T09:58:46Z","updated_at":"2016-11-28T14:00:10Z","closed_at":"2016-11-28T14:00:10Z","body":"The only way to tie behavior to the X.509 client errors in libwebsockets, is to parse the libwebsockets log messages. Can you add a LWS_CALLBACK_CLIENT_X509_ERROR callback that provides the X509_V_ERR value to a client application?"}}
{"actor":{"display_login":"lws-team"}}