Kong can't match routes correctly with the same hosts, paths, and different protocols in the route. about kong HOT 4 CLOSED

Currently Kong can not identify http/https and grpc/grpcs, because grpc/grpcs are http/https protocol actually.

from kong.

Perhaps we could add some extra information to distinguish them (a special header?)

from kong.

Perhaps we could add some extra information to distinguish them (a special header?)

Thanks for your reply, it seems like it is possible to recognize a grpc request by the Content-Type in the header in the grpc protocol, I will try that.

from kong.

Perhaps we could add some extra information to distinguish them (a special header?)

I tried adding content-type:application/grpc,application/grpc+proto,application/grpc-web,application/grpc-web+proto to the headers, and so far it seems to be able to differentiate between grpc vs. http requests, thanks again, I will close this issue!

from kong.