Closed Bug 68694 Opened 24 years ago Closed 24 years ago

https connections hang

Categories

(Core Graveyard :: Security: UI, defect)

Product:
Core Graveyard
Component:
Security: UI
Version:
Other Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 31174

People

(Reporter: neil, Assigned: javi)

Details

I am unable to connect to https sites.  It seems as though the connection
times out.  This bug has been in the nightlies for several weeks.  I have to use
the M18 build in order to access secure sites.

e.g.
Error loading URL
https://trading.etrade.com/cgi-bin/gx.cgi/applogic+PortfolioMain: 80004005
Works for me. Try renaming your ~/.mozilla directory.
Assignee: ddrinan → javi
Status: UNCONFIRMED → NEW
Ever confirmed: true
Observed same behavior with Linux Build ID 2001021321, even after removing
.mozilla directory and starting fresh. I installed from installer package. Also,
my internet access is through a Netcache firewall. Possibly part of the cause,
when selecting the login button on the http://www.401k.com site, I get another
proxy authentication dialog (a known bug, I forget the number right now). I
enter my user id and password and OK the dialog, then the status bar says the
page is loading, but it sits at about 50% for a minute or so, CPU spinning at
100% all the time, then the timed out dialog comes up. After dismissing the
timed out dialog the CPU returns to normal.
Make sure that under the psmdata directory you have doc and ui directories. If 
you don't, that build bug is known so try the nightly build.
http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu.tar.
gz
Also, try a different secure site like https://www.verisign.com
I have tried removing .mozilla and still see the problem.  I checked
mozilla/psmdata and it has the two directories mentioned.  I see the same
problem with the verisign.com site.
Ack! I just noticed I forgot to mention in my first report that I am connecting
through a proxy server.  The proxy server uses port 8088.

Then could your situation be a dupe of bug 31174 ?
Re bug 31174

Yes looks like it.  Sorry, this bug did not show up in the query I ran before I
submitted.



*** This bug has been marked as a duplicate of 31174 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.