I've had this happen. I even sent it in as a bug prior to the latest release. not fixed you notice. another bug i reported was fixed. for local web server content, 127.0.0.1 would work and localhost would not. you think no biggy i can work around that just use 127.0.0.1 all the time, yeah well it would on some links switch from 127.0.0.1 to localhost and then blow it