i think there is a bug in web shield some browsers can't be scanned

[taketez]

【5.0.462】

I have edited the WebShield.ini in C:\Users\All Users\Alwil Software\Avast5,and add sth.

   in order my browser can be scanned by WebShield

i changed it like this :

[WebScanner]
WebScanning=1
IntelligentStreamScanning=1
HttpRedirectPort=80
IgnoreAddress=
IgnoreLocalhost=1
OptinProcess=SogouExplorer.exe,SaaYaa.exe
[Common]
ProviderEnabled=1


but i found,the SaaYaa can  be scanned,but the SogouExplorer can not!

I have tried many times,I found that if the name is longer than 10 letters,it can't be scannd.

I think it's a bug~~

[DavidR]

The fact that you have used the optin for the browser doesn't necessarily mean it will be scanner or work, just that you are instructing the web shield to try to scan its traffic.

If the browser doesn't strictly conform to HTTP protocols then it will fail. So I'm not entirely certain there is any file name limit

[taketez]

the sogouexplorer,if i changed its name into sogou.exe ,the web shield can scan it .

[DavidR]

Weird.

[taketez]

It's a bug~~

[DavidR]

Well a bug is something which happens not as it was designed.

Who knows if that is the intention as most browser executables conform to an 8.3 format, so perhaps that is what the input format limit is.

Though there is a similar ini file option, IgnoreProcess option in the emailshield.ini and I'm able to enter my anti-spam executable MailWasher.exe which has a 10.3 format, so as I said weird and perhaps it is an omission having an input format of 8.3, rather than a bug.

[taketez]

thx

but I really hope avast can improve this !