Well, if you control the server, you can attach a network monitor and see exactly what it receives from the client. My guess is that T-Mobile did not like the headers sent by your SE and somehow altered the HTTP request in a non-standard way. That triggered the abnormal server response. After all, 411 error is very rare.
To understand this properly, you need to intercept the traffic at socket level. I would suggest you to replace that remote IP with a server that you have control of. Then you can see what exactly is passed from the network. Please post back when you have solution.