{"action":"closed","issue":{"url":"https://api.github.com/repos/OWASP/O-Saft/issues/35","repository_url":"https://api.github.com/repos/OWASP/O-Saft","labels_url":"https://api.github.com/repos/OWASP/O-Saft/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/OWASP/O-Saft/issues/35/comments","events_url":"https://api.github.com/repos/OWASP/O-Saft/issues/35/events","html_url":"https://github.com/OWASP/O-Saft/issues/35","id":48086142,"number":35,"title":"Read error: Connection reset by peer ","user":{"login":"EnDe","id":103866,"avatar_url":"https://avatars.githubusercontent.com/u/103866?v=3","gravatar_id":"","url":"https://api.github.com/users/EnDe","html_url":"https://github.com/EnDe","followers_url":"https://api.github.com/users/EnDe/followers","following_url":"https://api.github.com/users/EnDe/following{/other_user}","gists_url":"https://api.github.com/users/EnDe/gists{/gist_id}","starred_url":"https://api.github.com/users/EnDe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EnDe/subscriptions","organizations_url":"https://api.github.com/users/EnDe/orgs","repos_url":"https://api.github.com/users/EnDe/repos","events_url":"https://api.github.com/users/EnDe/events{/privacy}","received_events_url":"https://api.github.com/users/EnDe/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/OWASP/O-Saft/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2014-11-07T14:19:08Z","updated_at":"2016-09-23T15:48:44Z","closed_at":"2016-09-23T15:48:44Z","body":"Sometime an error like follows is returned:\r\n    Read error: Connection reset by peer (,199725) at blib/lib/Net/SSLeay.pm (autosplit into blib/lib/auto/Net/SSLeay/tcp_read_all.al) line 535.\r\n\r\nThis most likely happens when the target resets the TCP connection when a HTTP GET is performed.\r\nThe error ocours in Net/SSLeay.pm and cannot be handled outside.\r\n\r\nHowever, up to now, all cases where this occours, the target responded with a valid HTTP response, either with a HTTP/1.1 900 status (which is very uncommon) or with a HTTP/1.1 30x status. "}}
{"actor":{"display_login":"EnDe"}}