> they care whether a particular TLS session says it's for this.example or that.example and the transactions will accordingly go to the correct place. This Mozi

> they care whether a particular TLS session says it's for this.example or that.example and the transactions will accordingly go to the correct place. This Mozilla behaviour doesn't cause any problems. Indeed they do - via the SNI header, which is set once per TLS connection, not once per HTTP request. I would think initializing a connection for one domain and then reusing it for a different domain could absolutely cause problems.