I’m using Kubernetes with an NGINX Ingress controller configured for HTTP/2 and a keep-alive timeout of 600 seconds (configmap).
Issue:
- I have configured HTTP/2 and set keep-alive to 600 seconds.
- When I open my application in Chrome and send a few initial requests, they complete successfully.
- After waiting for 2-3 seconds and then sending another batch of requests, I expect Chrome to reuse the existing HTTP/2 connection. However, it seems like Chrome is reinitializing the connection instead of reusing the existing one, resulting in a noticeable delay.
Questions:
- Why is the keep-alive timeout of 600 seconds not working as expected?
- Is there a specific reason why Chrome is not reusing the HTTP/2 connection even though it should remain open?
Any insights or solutions to ensure that Chrome reuses the HTTP/2 connections properly would be greatly appreciated.
Thank you in advance for your help!