Sven wrote:
I'm certainly not the first to write about this subject, but I came
across it after buying a new PC with NIS on it and it messed up my
site without telling or yelling.
I solved it by this statement in the <head></head>
<script src=http://www.mydomain.co m/norton.js></script>
and the script at http://www.mydomain.com/norton.js contains the
follwing code:
<snip> It works for me.
You have wasted your time. You have encountered one specific
configuration of one version of a content inserting/re-writing proxy
(operating as an Internet security program) and attempted to reverse its
actions. Norton don't have to do much to render your script obsolete
(change the names of the functions it uses), and very little more to
render its entire strategy invalid (e.g. dynamically generate the
function names, or closure-wrap the original functions so that they
become inaccessible to other scripts on the same page, and so cannot be
restored by local scripts). And every other content-inserting/re-writing
proxy is still having a similar effect on your site. (and if the
significant problem is the opening of new windows then every pop-up
window blocking technique is probably having a similar detrimental
effect).
Trying to fight these things is just going to provoke an arms race, in
which the software operating on the client computer will always be able
to win because it doesn't have to overburden a web site by downloading a
huge mass of script as its contribution to the fight.
The solution that works, and works for everyone, is to stop relying on
the ability to do things that users (and the writers of Internet
security programs) regard as potential sources of abuse (i.e. not trying
to open new window, not relying on ActiveX, etc,).
Richard.
