Lucern, webshield is a tool that filters network traffic. Most bugs in the tool manifest themselves as problems with network. I am not saying that we have no bugs in WebShield. Not at all, however presenting this situation in a way that we know about bugs and don't fix them - this is what I might see as insulting of our work.
Yes, there is probably a bug in the code, since you are reporting it. Several guys from the StreamFilter team are trying to find a solution for your problem at the very moment, 23:45 in the middle of the night.
The second highest option 35.8 % does not reflect what has changed after people voted. I have posted this thread when a patch to aswstm.sys was available and since that we have made several bug fixes and we have also released a new version. Several problems, such as the problem with Dropbox upload (see elsewhere), was fixed with the 2013 update, and these fixes were introduced after the vote you are referring to.
So, I what I claim is that more problems were fixed that is recorded in this poll. You might believe otherwise of course and since on your system the WebShield component does not work correctly, you have every right to be unhappy and even angry at us. Sorry for that.
This is why I have suggested you to switch to the proxy mode, it is functionally equivalent to the streamfilter and shouldn't have the same issues. If you are already angry, there is no need for you to be more angry troubleshooting the bug for us if you don't want to. If it's just you on the whole earth, you would be happy and problem solved. That is however not very probable, so others might help us find out more about the issue or we might be eventually able to reproduce the issue ourselves.
My answer is: If you switch to proxy you don't have to do anything manually again. You'll be switched to proxy for ever and running what you were running in avast 9.0.2008. Your protection will be the same as it ever was. And it is possible that in the future we might turn you back on on streamfilter mode. Currently that's not what we do or plan to do - so if you would like to give streamfilter a try in the future, you would have to do it your self (I imagine how angry you might be if all of a sudden all your problems would come up again just from the fact that we thought that this was fixed since it was fixed for other users - yet in your case, things might be different)
Second answer might be: We might also switch all users to proxy. We would do that if the number of problematic cases would be higher. Say something more than 39 / 80.000.000. The number of users with problems is of course much higher than 39 in every 80 millions (but nowhere near 39% or even 3% percent), we are aware of that and the guys on the support lines and emails are trying to help each individual. There are users with WebShield proxy problems and there are users with WebShield StreamFilter problems and the support team is trying to help both parties. Since the 9.0.2013 the number of users with problems with Streamfilter is much lower and that also support my belief that many bugs were fixed.
Third comment: when I say a bug was fixed, I mean that we have seen a problem, we have found out what the cause of the problem was and we have removed the caused == fix. Then, we have verified that particular problem went away on systems where it was previously visible. I can not possibly guarantee that there are other cases which are not yet covered which we haven't seen yet. However, I never acknowledge a fix here, if we haven't fixed the bug.
So, to sum up: what you are saying is not true. We are not aware of a unfixed bug for months and we don't ignore it. Other, unfixed bugs are still being researched and will be fixed as soon as we can.
Regarding you logs:
firstly: you've uploaded an empty folder.
secondly: you've uploaded a log file without any captured traffic == no problem
third: you've uploaded usable logs, which are being looked at, nothing particular that might help is recorded, as it seems now. That's why I have sent you a step by step info, how to record better logs - only if you want of course.
Regarding the threads:
E.g. Lermanfl is mentioning he is running Windows Vista - this a typical case, when shouting does not help: Vista is not capable of executing streamfilter code, aswstm.sys driver does not run there. Clearly this is not something related to the case we are talking here about. No patch might possibly help, since the driver being patched is not even installed on Windows Vista. Even the bugs in the HTTP parser code related to other issues is not related to this specific (sad) case - this is COMPLETELY UNRELATED.
So my question is: What about proxy mode? Does that help at your case? Since if it does not, we might stop searching for a bug in the streamfilter code - the problem must be elsewhere (possibly same as Lermanfl is reporting, but definitely unrelated to stream filter). So far we believe it is a streamfilter code, since the code is new and had smaller time to settle. Even if it eventually will turn out that it wasn't there - it wouldn't hurt us to make a thorough revision of the code (which is what we do now) and the testing tools being implemented these days will come handy in future as well - but definitely all these efforts wouldn't (in such case) help to solve your specific issue.
L.