I was part of betatesting for the version of AdAware 2007. I was reporting
that update in AdAware 2007 doesn't work when connected through proxy.
Unfortunately there was no fix yet.
Now I am user of personal copy of released AdAware 2007 FREE and still no
fix in the latest 7.0.2.3 version.
I was so frustrated, that I started to do some reverse-engineering. Here is the result:
1) the problem is in the Update.dll component
2) when connected through proxy to download site using CONNECT
download [dot] lavasoft [dot] com:443 HTTP proxy command, the implementation in
component Update.dll expects that proxy respond by "200 connection
established".
3) but unfortunately after successful CONNECT command, our proxy responds by
"200 ok", which doesn't match expected "200 connection established" and
connection is closed on your part. So the update never succeeds with the infamous SSL Web Update Error dialog.
4) the solution should be either compare only the first numerical value
"200" in this case or use the "Response code:" header of response headers,
which lists only the exact response numerical value (200 in case of
success). Using this solution, the implementation should be independent of
proxy type and version used. In HTTP protocol documentation IS recommended
NOT TO USE the response string as reference. After the numerical value,
anything can be written until the new line character.
5) Just to remove all doubts, the proxy is the Cisco official proxy solution - no home-build one.
I hope my explanation is clear, if not, please let me know, I am ready to
answer any question.
Thanks,
Daniel