I go shopping for a compass, then my Sonos decides it needs one too
Last night I spent some time online looking to buy a compass. I looked at many of the Suunto models. Also yesterday I installed Little Snitch after noticing that an unknown
gamed process wanted to establish a TCP/IP connection.
Anyway… a few minutes ago, 10 or 11 hours after I eventually bought a compass, a message pops up from Little Snitch telling me that the Mac OS X desktop Sonos app was trying to open a connection to
ns.suunto.com. See image on right (click for the full-sized version).
Can someone explain how that works? Either Little Snitch is mightily confused or…… Or what? Has the Sonos app has been digging around in my Chrome browser history or cache or cookie jar? Is Chrome somehow complicit locally? Or something with cookies (but that would require the Sonos to be accessing and sending cookies stored by Chrome). Or…. what?
ns.suunto.com? There’s an HTTP server there, but its
/ resource is not very informative:
$ curl -S -v http://ns.suunto.com * Rebuilt URL to: http://ns.suunto.com/ * Hostname was NOT found in DNS cache * Trying 188.8.131.52... * Connected to ns.suunto.com (184.108.40.206) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.37.1 > Host: ns.suunto.com > Accept: */* > < HTTP/1.1 404 Not Found * Server Apache is not blacklisted < Server: Apache < Content-Type: text/html; charset=iso-8859-1 < Date: Wed, 10 Dec 2014 16:02:47 GMT < Content-Length: 16 < Connection: keep-alive < * Connection #0 to host ns.suunto.com left intact File not found."⏎
Unfortunately, Little Snitch doesn't tell me the full URL that the Sonos app was trying to access.
Anyone care to speculate what's going on here?