1813

how you're doing with it today?

[smallcompany]

There was quite of debate in the past about this AV based thing, however you would call it. I noticed that it’s still generating a lots of 404s in cases where I have “?someting” variables attached to my URLs, plus it’s having trouble with loading a particular JavaScript file where it starts multiplying subfolders almost indefinitely. To a link as mysite/script/script.js this thing would just keep adding a subfolder like mysite/script/ script/script.js, mysite/script/ script/ script/script.js, and so on...

It looks like it has a problem with reading links that are relative to a document.

Do you have the same problem or any other with this 1813?

Are you blocking it? Should we all block it, or we should not?

Thanks

[wilderness]

The threads on this were literally BEAT into the ground and yet you desire more?

[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]

[dstiles]

It's still a problem, denoting a high number of vulernable AVG users out there (major updates on AVG8 recently so they are probably already infected).

For the record, on one server (about 50 sites) I've seen over a thousand 1813-type hits in the past fortnight. Some of these were multiples within the same "scan". On another server over the same period, one site, over 1500 spread in groups of one to five-ish.

[Samizdata]

AVG has recently produced some embarrassing false positives involving ZoneAlarm, Flash and Windows system files - this may explain the number of older versions that I am seeing, presumably downloaded earlier in the year and freshly-reinstallled.

I still serve "1813" a small dummy file with no apparent ill-effects.

...