{"action":"created","issue":{"url":"https://api.github.com/repos/varnishcache/varnish-cache/issues/2151","repository_url":"https://api.github.com/repos/varnishcache/varnish-cache","labels_url":"https://api.github.com/repos/varnishcache/varnish-cache/issues/2151/labels{/name}","comments_url":"https://api.github.com/repos/varnishcache/varnish-cache/issues/2151/comments","events_url":"https://api.github.com/repos/varnishcache/varnish-cache/issues/2151/events","html_url":"https://github.com/varnishcache/varnish-cache/issues/2151","id":192803555,"number":2151,"title":"Health probes do not honor a backend's PROXY protocol setting","user":{"login":"fgtham","id":1180356,"avatar_url":"https://avatars.githubusercontent.com/u/1180356?v=3","gravatar_id":"","url":"https://api.github.com/users/fgtham","html_url":"https://github.com/fgtham","followers_url":"https://api.github.com/users/fgtham/followers","following_url":"https://api.github.com/users/fgtham/following{/other_user}","gists_url":"https://api.github.com/users/fgtham/gists{/gist_id}","starred_url":"https://api.github.com/users/fgtham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgtham/subscriptions","organizations_url":"https://api.github.com/users/fgtham/orgs","repos_url":"https://api.github.com/users/fgtham/repos","events_url":"https://api.github.com/users/fgtham/events{/privacy}","received_events_url":"https://api.github.com/users/fgtham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-12-01T10:13:22Z","updated_at":"2016-12-05T14:27:25Z","closed_at":null,"body":"I'm using varnish-5.0.0 with PROXY protocol enabled on the backends thanks to the new `.proxy_header` attribute. This works great as long as the backends don't have health probes defined. When a backend has both a `.proxy_header` attribute and a probe defined, varnish fails to properly detect the backend health state and marks the backend as sick.\r\n\r\nThe problem seems to be that varnish does not use the PROXY protocol when sending health probes. If the backend correctly implements the PROXY protocol, it is required to drop the connection, as it cannot identify it as valid PROXY protocol v1 nor v2. Thus, from varnish's pov the backend is unreachable.\r\n\r\n## Possible Solution\r\nHealth probes should honor the backend's `.proxy_header` attribute and send the correct PROXY header where appropriate.\r\n"},"comment":{"url":"https://api.github.com/repos/varnishcache/varnish-cache/issues/comments/264867193","html_url":"https://github.com/varnishcache/varnish-cache/issues/2151#issuecomment-264867193","issue_url":"https://api.github.com/repos/varnishcache/varnish-cache/issues/2151","id":264867193,"user":{"login":"fgsch","id":241785,"avatar_url":"https://avatars.githubusercontent.com/u/241785?v=3","gravatar_id":"","url":"https://api.github.com/users/fgsch","html_url":"https://github.com/fgsch","followers_url":"https://api.github.com/users/fgsch/followers","following_url":"https://api.github.com/users/fgsch/following{/other_user}","gists_url":"https://api.github.com/users/fgsch/gists{/gist_id}","starred_url":"https://api.github.com/users/fgsch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgsch/subscriptions","organizations_url":"https://api.github.com/users/fgsch/orgs","repos_url":"https://api.github.com/users/fgsch/repos","events_url":"https://api.github.com/users/fgsch/events{/privacy}","received_events_url":"https://api.github.com/users/fgsch/received_events","type":"User","site_admin":false},"created_at":"2016-12-05T14:27:25Z","updated_at":"2016-12-05T14:27:25Z","body":"@fgtham right, but since you are using the proxy protocol, how you differentiate (or are you planning to) requests coming from varnish (backend probes) vs coming from client (requests)?"}}
{"actor":{"display_login":"fgsch"}}