2 ms·
To be slightly pedantic, websockets specifically don't have HTTP headers like XFF, which is IMO part of the problem with Websockets -- you end up re-inventing b
by seanp2k2 10y ago
To be slightly pedantic, websockets specifically don't have HTTP headers like XFF, which is IMO part of the problem with Websockets -- you end up re-inventing basic functionality. IMO (and combined with other factors) this is a great reason to choose http/2 over websockets.
EDIT: ALB also supports http/2, but they can also do websockets as well as WSS (where you'd term SSL on the ALB for websockets).
- manigandham 10y agoHttp/2 and websockets are not interchangeable, you cant choose to use http/2 if you want a bidirectional lightweight communications protocol to the client. The initial upgrade http request from the client should have all the headers you need.