On Mon, 29 Jun 2015 11:11:12 -0500, VanguardLH wrote:

> The [part of the] program doing work doesn't run off of storage media.
> It is loaded in system memory and runs from there.  CPU and memory
> speeds are more relevant.

CPU: AMD A8-3870K Black Edition Quad-Core APU
RAM: 8 GiB DDR3 (2x4GiB; dual channel)
 
> > Haven't noticed this and I have the HTTPS Everywhere add-on installed in
> > Fx. Which site(s) and which browser(s) did you use to make a comparison?
> 
> That add-on has NOTHING to do with encryption.  That only tries to
> connect to an HTTPS version of a web page *if* available.

So I probably encounter /more/ HTTPS websites than someone who doesn't
have the add-on installed. (My point being.)

> >> The proxy will get changed to 127.0.0.1 (no port assigned).

> > Doesn't happen here.
 
> How often do you check if IE is using a proxy or not?  Did you check
> immediately after you got the "page can't be displayed" error in IE?

I hardly use IE. I'm not going to check its settings every time I open a
web page with it. You mean the proxy settings are changed and then
changed back again?
 
> >> So run certmgr.msc to see if Avast's cert was added.  

> > It's there alright. Says something about 'Server Authentication '.
 
> Then the problem with non-connectivity is Avast's transparent HTTPS
> proxy went unresponsive.  When proxies go dead, usually you have to kill
> the process and reload it (which may require more than one process kill
> and then loading them in the correct order).  Typically the cure is to
> shutdown Windows and reboot.

I added https://startpage.com* (and several other addresses) to the
exclusions and everything runs fine now.

-- 
s|b
--- NewsGate v1.0 gamma 2