Kong with http2 and coalescing about kong HOT 2 CLOSED

Thanks for providing a solution. While returning 421 from Kong gateway does not satisfy the specification of HTTP/2:

 This status code MUST NOT be generated by proxies.

See: https://datatracker.ietf.org/doc/html/rfc7540#section-9.1.2

What is the current behavior when the connection is incorrectly reused? I think Kong gateway will return 404 if no host is matched. You could try to update the certificates for sites in different envs and do not use the certs allowing wildcard hosts. So the allowed host in certificates for different envs will not overlap, then browsers cannot reuse the same connection for different hosts.

from kong.

Thanks for the response.

Yes kong will return 404 as the host and therefor the route can't be found.

We will consider your solution. An other solution could be to use a external load balancer as ingress type in k8s.

Will close the issue thx

from kong.