Closed Bug 75237 Opened 23 years ago Closed 23 years ago

SSL behaves incorrectly w/httpS proxy requiring authentication

Categories

(Core Graveyard :: Security: UI, defect)

1.0 Branch
x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME
psm2.0

People

(Reporter: le_jawa, Assigned: ddrinan0264)

References

()

Details

(Keywords: crash, stackwanted)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8.1)
BuildID:    2001040904

See bug #67465.  When browsing from behind a firewall and trying to access sites
that use certificates, Mozilla crashes or freezes.  If you try to access the URL
https://www.palm.net/Registration/RegistrationNewUser.jsp?doSSL=1 for example,
Mozilla will prompt you for a firewall id and password  (bug 67465).  If you
enter your id and pass, Mozilla will crash or freeze while trying to render the
page.  Which happens seems to depend on the build.  2001040904 freezes


Reproducible: Always
Steps to Reproduce:
1.Access the site mentioned above.
2.Enter id and pass
3.Click 'OK' and watch her go down...

Actual Results:  No prompt and no crash

Expected Results:  Prompt and crash
Reporter do you have the talkback ID or stacktrace from the crash?
Unfortunately, no.  It's been a while since a build actually crashed.  Most of
the more recent builds just freeze.
Keywords: crash, stackneeded
Reporter, is this still a problem now that PSM 2.0 is in the nightly builds?
Status: UNCONFIRMED → NEW
Component: Security: Crypto → Client Library
Ever confirmed: true
Product: Browser → PSM
Target Milestone: --- → 2.0
Version: other → 2.0
Let me put this into bullets.  I've noticed a lot here lately and it will be
easier to follow this way (I hope.)

1.)  Mozilla no longer crashes or freezes when accessing certificate-enabled
sites.  Yeah!
2.)  Mozilla still prompts for a firewall id and pass when accessing these sites
from behind a firewall.
3.)  Rather than crash (***or go to the desired page***), Mozilla sends the user
to the firewall's HTML page.  Better than a crash but still a problem...
4.)  I tried out the expiramental build from the 23rd.  It did NOT prompt me for
my firewall login, but instead fired up my default browser (sorry, at work it
has to be IE) and opened the page there.

In case the info is useful, the firewall brand is Interlock.
Reporter, what are your proxy settings?  Do I correctly understand that you are 
using https between Mozilla and the firewall?

Changing Summary.
Summary: Mozilla crashes when trying to access certificate sites from behind a firewall → SSL behaves incorrectly w/httpS proxy requiring authentication
Most software I use with the firewall works when I set it to https, but we 
actually connect to it via port 80.  Of course, user id and password 
authentication are required.  Our HTTP connection, FTP and security are all 
configured on our browsers to use port 80 or port 81 (only used if 80 doesn't 
work).
I'm sorry, I don't understand what settings you are using.  Please report what
value is entered for each field of the Edit/Preferences/Advanced/Proxies dialog box.

This is possibly a duplicate of bug 75865.  Please retry with a build made on or
after 4/30.
Tried that.  Everything is behaving well except one annoying little thing.  I
still get prompted to login to the firewall when accessing my webmail site
(https://mail.xmission.com).  

It looks like at least this bug has been fixed, and the dialog bug is documented
in bug #67465.  More new comments there.

I recommend closing this bug as resolved.  Fantastic work!
Marking WORKSFORME based on reproters comments.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.