Thanks for excellent support!
We are using Kong 0.14.1 and enabled and tried enabling the http2 by updating the yaml for kong to enable http2 on both admin and proxy ports. Now we see an issues that service that support http2 are able to talk to kong but not the apps that support http 1.1.
I was under the assumption that enabling http2 means that the proxy is backward compatible…Did I miss anything Or do we need to handle it with some configuration on admin or adding some config data in our yaml for kong?
Kong Configuration change:
Kong values.yaml modification via helm:
containerPort: “8443 http2”
@@ +29,36 @@