Last modified: 2014-05-19 21:50:24 UTC
My guess is this might be somehow related to framing. However, it uses: webHost : window.location.hostname which in theory should work even in a framing scenario, unless the context of the JavaScript was somehow lost. On http://jsfiddle.net/596mX/ the top web host is htp://jsfiddle.net, the frame host is http://fiddle.jshell.net, and it alerts the latter's hostname.
Thanks for bringing this up and for linking the other ticket, this is an issue that we should take very seriously as people crunching the data will rarely remember to filter by webHost (assuming filtering by wiki is sufficient) which will cause the inclusion of a lot of bogus events caused by test instances on labs or legitimate but spurious events caused by users with proxies or other factors. I think we should try and enforce stricter validation for the webHost field to only accept events from a list of known hostnames and set up monitoring of events that fail validation on the webHost field.
Steven also suggested it could be related to Chrome's automatic translation feature. My tests indicate that still uses the original hostname in Chromium 34.0.1847.132 Debian 7.5 (265804) , but this behavior might vary by version or something.
