Closed
Bug 112770
Opened 23 years ago
Closed 23 years ago
"The connection was refused..."
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: erik.fornoff, Assigned: neeti)
References
()
Details
Environment:
==============
OS: Win NT 4.0 SP-6
Mozilla BuildID: 2001112803
Summary:
=========
When trying to get to the SSL-Login of the above mentioned freemail-service I
get the error-message:
"The connection was refused when attempting to contact freemail.web.de"
Reproducible: always
Steps to Reproduce:
====================
1. Start Mozilla
2. Enter "www.web.de" in the location bar
3. On the right side of the upcoming page you'll find 2 datafields to enter
username / password along with a pushbutton called "Login". Right next to this
pushbutton you should find a link "SSL-Login" => click this link!
Actual Results:
================
Error message "The connection was refused when attempting to contact
freemail.web.de" appears...
Expected Results:
==================
The page allowing to login via SSL appears...
Additional Information:
========================
The error is not caused by the fact, that you first have to enter user name and
password! Normally if you click this SSL-Link a new page with datafields for
username + password appears...
Note: Using Netscape 4.51 and MSIE 5.5 everything works fine.
PSM is installed and the setup for SSL Protocol versions looks like the following:
SSL V.2: enabled
SSL V.3: enabled
TLS: disabled
|
||
Comment 2•23 years ago
|
||
-necko
Assignee: asa → neeti
Component: Browser-General → Networking
QA Contact: doronr → benc
WFM win98, w2k build 2001120303
...after clicking "SSL-Login" a get a dialog box that says 'There is a problem
with the certificate that identifies "freemail.web.de". Do you want to
continue? The certificate was issued by a certificate authority that Mozilla
does not recognize.' If I click "Continue" I get the logon page, but I
haven't gotten a "connection refused" message yet.
*** Bug 112773 has been marked as a duplicate of this bug. ***
Finally I found the cause of this problem - the port of our SSL proxy has been
changed so I will change the resolution of this bug to "invalid"...
Cheers, Erik
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
There should be a bug that talks about how lousy our error messages are for
proxy errors...
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Whiteboard: dupeme
|
||
Comment 7•23 years ago
|
||
*** This bug has been marked as a duplicate of 56629 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupeme
You need to log in
before you can comment on or make changes to this bug.
Description
•