15 ms·
I'm curious as to how everyone deals with HTTP/2 requirements between the backend servers and the load balancer? By default, HTTP/2 requires TLS which means eit
by ksajadi 2y ago
I'm curious as to how everyone deals with HTTP/2 requirements between the backend servers and the load balancer? By default, HTTP/2 requires TLS which means either no SSL termination at the load balancer or a SSL cert generated per server with a different one for the front end load balancer. This all seems very inefficient.
- kcb 2y agoNot sure how widespread this is but AWS load balancers don't validate the backend cert in any way. So I just generate some random self signed cert and use it everywhere.
- nhumrich 2y agoYou don't need http2 on the actual backend. All limitations for SSE/http1 are browser level. Just downgrade to http1 from the LB to backend, even without SSL. As long as LB to browser is http2 you should be fine.
- ksajadi 2y agoIsn't that going to affect the whole multiplexing / multiple connection of SSEs?
- seabrookmx 2y agoI don't think so? HTTP 1.1 still supports Keep-Alive.
- nhumrich 2y agoNo. That's all handled in the browser and load balancer.