4 ms·
sounds more like your firewall filtering is broken.
by eli 18y ago
sounds more like your firewall filtering is broken.
- DenisM 18y agoWhen I read to the end I found that author proposes a mechanism that is far less convoluted than google's and devoid of this similar problems. It's better to have less code in your page and more code in google's script - that way they can patch it without me getting involved. As it is now they added the try/catch block (really helps if users run ad-block or some such) but most web admins have not updated their stuff.
- eli 18y agoThough he accomplished it by altering the requirements. His solution does not work seamlessly with HTTPS sites -- it requires a server-side changes to the code. That's a pretty big issue for a script that's supposed to "just work."
- DenisM 18y agoBut it doesn't "just work" - it breaks it the face of some firewalls and pops an exception if user has adblock. I actually had users complaining about the latter, this is not a theoretical problem (I fixed it with try/catch myself, but it should not have been a problem to start with and demonstrates brittleness of google analytics). In other words it's a tradeoff between http/https transparency and odd errors on user's end. Pick your poison. :-)
- briansmith 18y agoThese "broken" firewalls are becoming increasingly common. Besides that, IE8's private browsing mode automatically blocks Google Analytics and similar tracking services (and ad networks?). Look for that to be increasingly common in web browsers that care more about the end user than they care about advertisers. By the way, what was "broken"? In this case, everything worked out fairly well for everybody except the website owner and Google, who are likely indifferent to the negative result. Google Analytics doesn't provide any functionality to the user so it doesn't matter to him if the script fails to load or not. The page probably loaded a little faster and his web browser is probably using a little less memory. He probably also got to preserve just a little bit more privacy. The IT team that deployed the firewall got paid to do so and plus they can feel good knowing that their firewall is probably blocking some actual XSS attempts. That reduces IT costs for the company. The manufacturer likely got paid a lot of money for the firewall and the sales guy probably made a nice commission on it.