Arthur
06-04-2001, 07:46 AM
They're now stuffing 4 bookmarks into every surfer's fave list. I thought their initial no-banner policy was too good to be true, and it was. Now I've got pissed surfers who think it's my fault.
For the geeks, they call counter.js, whose code is an attempt to prevent casual tracing by disguising the address's individual characters with ordinal values. It resolves in part to this string, which is referenced as encoded jscript:
http://205.134.182.151/ads2/hstg/mchd/a3.jpg
Yes, a jpg! I'm curious what is happening here. I suspect a script at address 205.134.182.151 is examining who's calling a3.jpg. If it's referred from "counter.js" then it uses that notorious activex bookmark. If it's called as a direct request, e.g. someone snooping, then it shows a small jpg graphic. Nasty, but very clever...
Anyone the wiser on this?
For the geeks, they call counter.js, whose code is an attempt to prevent casual tracing by disguising the address's individual characters with ordinal values. It resolves in part to this string, which is referenced as encoded jscript:
http://205.134.182.151/ads2/hstg/mchd/a3.jpg
Yes, a jpg! I'm curious what is happening here. I suspect a script at address 205.134.182.151 is examining who's calling a3.jpg. If it's referred from "counter.js" then it uses that notorious activex bookmark. If it's called as a direct request, e.g. someone snooping, then it shows a small jpg graphic. Nasty, but very clever...
Anyone the wiser on this?