Is this phenomenon related to why websockets use masking? I believe it's something to do with shitty proxies being vulnerable to being cache-poisoned when an at

Is this phenomenon related to why websockets use masking? I believe it's something to do with shitty proxies being vulnerable to being cache-poisoned when an attacker sends data down the websocket (packet in packet) which looks like HTTP traffic.