While I did speed checking in the above referenced thread in Opera, it was afterwards I discovered it didn’t matter if avast! Web Shield was on or off, I got the speed range in Opera with Web Shield off, so I concluded Web Shield doesn’t work in Iron.
Next I went to Iron Tools (wrench icon)> Options> Networking> Change Proxy Settings & I get Internet Properties> Connections.
“Internet Properties> Connections” is for IE, so I guess a proxy can’t be set for Web Shield in Iron ???
I just thought : to check Web Shield & doesn’t show any change in last scanned or thread count no matter how many sites I visit, so that’s a confirmation that Web Shield isn’t working in Iron.
I don’t know if Iron is on the list of supported browsers, unfortunately there is no where that I’m aware of that you can check what is approved.
However you could opt-in Iron to use the web shield.
You need to edit the avast4.ini file [WebScanner] section and ad the executable file name for Iron.
[WebScanner]
OptinProcess=executableFileName.exe
Or you could set its proxy settings (in connections, don’t use Iron so don’t know the exact location) to use the web shield.
That’s IE settings your using to get Web Shield to work in Iron. It works. Evidently it’s a blanket setting for all browsers, even for Firefox, IE & Opera of which don’t need it. Just check “Internet Properties” in IE.
When you check the "Change Proxy Settings in Iron, it brings up the IE settings properties.
Your correct, setting your proxy in IE makes it Universal if the same settings are made in avast.
There is another avast option that I have used for the past couple of years - so much simpler than all this wondering.
Override (AYOR) the avast list of “acceptable” processes for http scanning - don’t worry about “Optin” processes - don’t worry about proxy settings …simply in the [WebScanner] section of the avast4.ini file add the line:
Optin=0
Then all http accesses by any process (your email client, any flavor of browser, application) gets scanned by avast.
You’re welcome, I prefer this to having to adjust and browser settings.
Whilst Alan’s suggestion works, it opts-in everything that uses the HTTP port 80 (as Alan mentioned) gets scanned, we have had some issues in the past with some programs using port 80 but not the http protocol. I think that is why the list of supported browsers was created, it also got round a weakness in some firewalls, ‘sygate’ that didn’t challenge anything using the web shield localhost loopback proxy as ashWebSv.exe was allowed.
It has always seemed to me a bit odd to scan http accesses by some browsers and yet to leave other http accesses unscanned (think how much http accessing is done now in e-mail clients) and just about every Tom, Dick and Harry application is now going out to the Web using http to see if there are updates available.
I prefer the safety of having all of them scanned by avast - if there is an application that does have a problem then there is an option in the same section to ignore that process.
to check Web Shield & doesn’t show any change in last scanned or thread count no matter how many sites I visit, so that’s a confirmation that Web Shield isn’t working in Iron.