-
pixelate joined the channel
-
Lecherito has quit
-
bkeys has quit
-
bkeys joined the channel
-
rmz_la3lma joined the channel
-
rmz_la3lma has quit
-
rmz_la3lma_ joined the channel
-
rmz_la3lma_ has quit
-
rmz_la3lma joined the channel
-
rmz_la3lma has quit
-
bkeys has quit
-
bkeys joined the channel
-
bkeys has quit
-
altr joined the channel
-
altr
hi
-
Is is possible to load balance grpc and https/web traffic on the same ip. I tried it with caddy but i get a http preface error
-
same ip and same port
-
so both on port 443?
-
ejona
altr: you should be able to if you are proxying. But gRPC requires HTTP/2, so that may be your problem.
-
altr
mm ok. Probably did something wrong :)
-
Any suggestions for the proxy software?
-
-
ejona
I've not used caddy myself, but I have looked at it some. I thought it would be able to do HTTP/2.
-
nghttpx is pretty common right now, or things built on the same library, like envoy.
-
lukasa
Caddy can do HTTP/2
-
ejona
Yeah, I thought Caddy should be able to do both inbound and outbound HTTP/2.
-
lukasa
It's not clear to me that Caddy can do *outbound* HTTP/2
-
But it can definitely do inbound HTTP/2
-
ejona
Actually, it would probably only do outbound HTTP/2 if using TLS, which probably isn't the case.
-
altr: Is it safe to assume you're doing plaintext (no SSL/TLS) from the proxy to the backend?
-
altr
yes
-
im using an insecure connection there
-
ejona
Then I'd expect the error you got was when Caddy is acting as a client to the backend.
-
altr
or could it be that caddy is proxying the traffic from http2 -> http
-
and grpc always expects http2 right?
-
ejona
The grpc protocol is HTTP/1.1-safe (assuming trailer support), but the implementations only speak HTTP/2.
-
So yeah, grpc expects http/2.
-
altr
mm maybe that is the issue. Ill do some more testing
-
thanks
-
altr has quit
-
so joined the channel
-
imouto joined the channel
-
bkeys joined the channel
-
bkeys has quit
-
bkeys joined the channel