Comment 15 for bug 314713

I have progress to report on this issue!

The problem seems to be related to transparent proxying of https at my ISP. If I manually specify the proxy server in my browser (on a port other than port 80) everything works correctly. It may have something to do with the router or NAT who knows. But I don't get the problem under windows. I've contacted TPG about this issue also. Hopefully knowlege will grow. I think its safe to say it is not DNS related - I've tested that to death.