{"action":"created","issue":{"url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/93","repository_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy","labels_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/93/labels{/name}","comments_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/93/comments","events_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/93/events","html_url":"https://github.com/vfarcic/docker-flow-proxy/issues/93","id":197617878,"number":93,"title":"HTTP/2 support ?","user":{"login":"myuseringithub","id":7758497,"avatar_url":"https://avatars3.githubusercontent.com/u/7758497?v=3","gravatar_id":"","url":"https://api.github.com/users/myuseringithub","html_url":"https://github.com/myuseringithub","followers_url":"https://api.github.com/users/myuseringithub/followers","following_url":"https://api.github.com/users/myuseringithub/following{/other_user}","gists_url":"https://api.github.com/users/myuseringithub/gists{/gist_id}","starred_url":"https://api.github.com/users/myuseringithub/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/myuseringithub/subscriptions","organizations_url":"https://api.github.com/users/myuseringithub/orgs","repos_url":"https://api.github.com/users/myuseringithub/repos","events_url":"https://api.github.com/users/myuseringithub/events{/privacy}","received_events_url":"https://api.github.com/users/myuseringithub/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2016-12-26T20:30:09Z","updated_at":"2017-04-04T05:01:29Z","closed_at":"2017-01-16T21:41:12Z","body":"Hi, I don't see any mention about http/2 support, this is crucial for modern web apps. Will it be added ?\r\n\r\nIf you could make this project pluggable it would make more sense, e.g. not limited to a default proxy. The project solves a lot and prevents maintenance of many different tools, but if it would be separated from using a specific proxy & limited configurations it would make more sense. I, for example, would like to test \"redbird\" proxy as it uses nodejs (https://github.com/OptimalBits/redbird), and it has some good features. But both of your projects mix a lot of the same features/components, if they are available separated and pluggable it would make more of custom & powerful combinations. \r\n\r\nThanks so much for your book & all examples. "},"comment":{"url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/comments/291393942","html_url":"https://github.com/vfarcic/docker-flow-proxy/issues/93#issuecomment-291393942","issue_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/93","id":291393942,"user":{"login":"teohhanhui","id":548843,"avatar_url":"https://avatars0.githubusercontent.com/u/548843?v=3","gravatar_id":"","url":"https://api.github.com/users/teohhanhui","html_url":"https://github.com/teohhanhui","followers_url":"https://api.github.com/users/teohhanhui/followers","following_url":"https://api.github.com/users/teohhanhui/following{/other_user}","gists_url":"https://api.github.com/users/teohhanhui/gists{/gist_id}","starred_url":"https://api.github.com/users/teohhanhui/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/teohhanhui/subscriptions","organizations_url":"https://api.github.com/users/teohhanhui/orgs","repos_url":"https://api.github.com/users/teohhanhui/repos","events_url":"https://api.github.com/users/teohhanhui/events{/privacy}","received_events_url":"https://api.github.com/users/teohhanhui/received_events","type":"User","site_admin":false},"created_at":"2017-04-04T05:01:29Z","updated_at":"2017-04-04T05:01:29Z","body":"> Swarm does L4 proxy and is incapable of evaluating request paths,\ndomains, and so on. It cannot forward to a specific service based on\nrequests. HAProxy, nginx, and a miriad of others are L7 proxies that can do\nthat.\n\nI didn't make myself clear. What I mean is that HAProxy is not a\nparticularly good HTTP + TLS proxy, as can be attested to by the fact that\nit still doesn't support HTTP/2. I thought its strong point is that it's a\ngood load balancer, so what do we gain by using it over nginx (which is a\npretty damn good HTTP + TLS proxy)?\n\nOn 4 Apr 2017 04:42, \"Viktor Farcic\" <notifications@github.com> wrote:\n\n> @teohhanhui <https://github.com/teohhanhui>\n>\n> Or indeed a docker-flow-proxy that uses nginx under the hood would be\n> perfect.\n>\n> DFP code can be extended to support nginx as well. Indeed, the initial\n> idea is to support multiple proxy backends. The only problem is time.\n> There's never enough. Would you like to help? If you could, I'm sure that\n> we could add nginx support.\n>\n> What does HAProxy bring to the table when it's not doing any\n> load-balancing (since that's left to the Swarm routing mesh)?\n>\n> Swarm does L4 proxy and is incapable of evaluating request paths, domains,\n> and so on. It cannot forward to a specific service based on requests.\n> HAProxy, nginx, and a miriad of others are L7 proxies that can do that. If\n> you'd use only Swarm network, every service would need to expose a\n> different port. If your cluster has only one public service, there's no\n> need for anything else. If, on the other hand, you do have more, you'll\n> need some kind of L7 proxy.\n>\n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/vfarcic/docker-flow-proxy/issues/93#issuecomment-291267451>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/AAhf6wBFmqGj35RGjULDz2I-gW2Umeypks5rsVmagaJpZM4LV6EA>\n> .\n>\n"}}
{"actor":{"display_login":"teohhanhui"}}