{"action":"reopened","issue":{"url":"https://api.github.com/repos/varnish/hitch/issues/276","repository_url":"https://api.github.com/repos/varnish/hitch","labels_url":"https://api.github.com/repos/varnish/hitch/issues/276/labels{/name}","comments_url":"https://api.github.com/repos/varnish/hitch/issues/276/comments","events_url":"https://api.github.com/repos/varnish/hitch/issues/276/events","html_url":"https://github.com/varnish/hitch/issues/276","id":344790632,"node_id":"MDU6SXNzdWUzNDQ3OTA2MzI=","number":276,"title":"Wrong default certificate with no SNI after certificate removal and hot-reload","user":{"login":"bago","id":173498,"node_id":"MDQ6VXNlcjE3MzQ5OA==","avatar_url":"https://avatars1.githubusercontent.com/u/173498?v=4","gravatar_id":"","url":"https://api.github.com/users/bago","html_url":"https://github.com/bago","followers_url":"https://api.github.com/users/bago/followers","following_url":"https://api.github.com/users/bago/following{/other_user}","gists_url":"https://api.github.com/users/bago/gists{/gist_id}","starred_url":"https://api.github.com/users/bago/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bago/subscriptions","organizations_url":"https://api.github.com/users/bago/orgs","repos_url":"https://api.github.com/users/bago/repos","events_url":"https://api.github.com/users/bago/events{/privacy}","received_events_url":"https://api.github.com/users/bago/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":23,"created_at":"2018-07-26T10:41:57Z","updated_at":"2018-08-23T10:16:20Z","closed_at":null,"author_association":"NONE","body":"I've upgraded from 1.4.4 to 1.4.8 in a \"multihomed\" setup (multiple IPs with their own certificates and multiple certificates for each IP). I had to skip 1.4.5, 1.4.6 and 1.4.7 because of issues handling the multihoming.\r\n\r\nNow, I just noticed that when the client does not support SNI, hitch 1.4.4 was using the FIRST \"pem-file\" for that frontend in the handshake. Now with 1.4.8 it sounds like with no SNI it uses a \"random\" certificate.\r\n\r\nCan you confirm the behaviour have been changed? Is it a bug or simply a change? Is there any workaround to force a specific certificate to be used when there is no SNI handshake?"}}
{"actor":{"display_login":"Dridi"}}