Frank Schröder

As for supporting gRPC: fabio can route HTTP and HTTPS and soon TCP. If gRPC can work with these transport protocols then it is already supported. What else would you...

The re-enable http/2 patch was a regression. HTTP/2 has been supported for incoming connections for quite some time but fabio still lacks the HTTP/2 outbound connections which is probably required...

From reading the docs this should just work out of the box. @jippi did you test that this doesn't work? I'll have a look this week.

@wv-myoung I can easily fork the `net/http/httputil` package for the moment until 1.9 is out and add the change if that's all it takes. I think I need to add...

ok, that's good to know. Then I'll add a gRPC test to the integration test and see where that fails.

@wv-myoung and @jippi I've pushed a change with a test. I think the main catch for enabling http2 is to call `http2.ConfigureTransport` in `main.go` since I didn't have to change...

@wv-myoung I'm not sure I understand the last statement. The upstream server needs `proto=https` since go does not support HTTP/2.0 without https? Why would the client need a tag? What...

Does gRPC work with HTTP 1.1? Go does not support HTTP/2 without TLS. The `tlsskipverify` option disables cert verification in fabio.

Well, if we can make it work with all transports then we should. I'll have a look whether I can make this work with http. Help is appreciated.

@DennisPersson Oh wow, I forgot about this one. I will have another look but if you want to help then this would be more than welcome.