HTTPS scanning blocks upload of pictures

[REDACTED]

I had to upload some pictures in a CMS system, which was using HTTPS. I couldn't upload them, the upload just died.

Turned off HTTPS scanning in Avast and it works again. 

[Asyn]

Which version of AIS..?

[REDACTED]

That was 2206. Gonna try out SP1 (2208) and see if it's fixed.

[REDACTED]

Nope still a problem in SP1.

[Asyn]

1. Download Avast Internet Security: http://files.avast.com/iavs9x/avast_internet_security_setup.exe
2. Follow instructions: http://www.avast.com/uninstall-utility (Run this tool for all prior installed Avast versions..!!)
3. Reinstall Avast with the downloaded installer from point 1.
4. Reboot.

[REDACTED]

Confirmed problem when uploading pictures on [1] flickr! Clearly a bug! Please fix..

[1] https://www.flickr.com/photos/upload/

[REDACTED]

Confirmed problem when uploading pictures on [1] flickr! Clearly a bug! Please fix..

[1] https://www.flickr.com/photos/upload/

Thanks.

I'm not reinstalling anything, as this is clearly a bug in Avast.

[lukor]

Hi guys,
I am sorry. I have to acknowledge the bug. We've been able to reproduce it with Firefox (IE seems without a problem, though). We are just analyzing the data. I'll keep you posted on any updates.

Thanks.
Lukas.

[REDACTED]

Thanks, that's great news.

[lukor]

Hi guys,
it seems we have been able to identify the bug. It is related to the way WebShield handles network buffers. Several things act together here - the size of the file/image being uploaded (>128KB) and the size of Winsock network buffer space for the connection (<128KB), together with the fact, that Firefox does not wait for the final SSL Handshake confirmation message before sending the payload.

We are working on a fix, it should be available here for testing in one or two days, when verified it'll be distributed most probably via emergency/micro updating mechanism.

Thanks.
Lukas.

[REDACTED]

Any update on this?

Still having this issue with HTTPS scanning.

[lukor]

Hi, we'll be releasing the fix on Tuesday or Wednesday this week. Thank you for waiting - the fix is already in QA for verification.