We need to re-consider the section on cross protocol attacks. The statement that is made is no longer true. The final answer will depend on the outcome of #1.
Discussed in SF Interim; feeling is that intermediaries that are this broken should be fixed, not worked around (as it's a problem with their implementation whatever we do).
Suggest bringing up in HTTPbis work if not there already, since this is more about 1.1 than 2.0.
We need to re-consider the section on cross protocol attacks. The statement that is made is no longer true. The final answer will depend on the outcome of #1.
RFC 6455, section 10.3 cites the following paper:
[TALKING] Huang, L-S., Chen, E., Barth, A., Rescorla, E., and C.
Jackson, "Talking to Yourself for Fun and Profit", 2010,
http://w2spconf.com/2011/papers/websocket.pdf.
This attack ultimately lead to thewebsocketsprotocol adopting a masking scheme. This needs to be considered.
The text was updated successfully, but these errors were encountered: