That's actually SockJS keeping a communication channel open between the browser and the web server, it's not downloading as such - note the reduced bandwidth you're seeing in your BandwidthIn graph after the first socket event (your line 13).
Here's a little more info via SockJS - https://github.com/sockjs/sockjs-client :
SockJS is a browser JavaScript library that provides a WebSocket-like object. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication channel between the browser and the web server.