Closed Bug 81166 Opened 23 years ago Closed 23 years ago

Mozilla doesn't render the page on a https URL

Categories

(Core Graveyard :: Security: UI, defect)

1.0 Branch
x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 79779

People

(Reporter: aleksander.adamowski, Assigned: ddrinan0264)

References

()

Details

Reproducible: always

To reproduce:
1. Go to https://kruczki:kruczki@office.altkom.com.pl/

Effect: 
Mozilla doesn't render the page, it only displays grey area.
When going to http://office.altkom.com.pl/, it works fine.

Mozilla versions affected:

win32-talkback downloaded from 2001-05-11-09/ (build id 2001051104) - works OK,
shows grey area for a second, then displays the page.
win32-talkback downloaded from 2001-05-11-16/ (build id 2001051104) - Mozilla
doesn't display the page, just plain grey area.
After about 2nd reload of the page, it shows it properly.
I also experienced an interesting behaviour with today's build
(from the 2001-05-14-22-trunk/ dir, build ID 2001051520):
When I do the following:
1. Visit any page (for example http://slashdot.org)
2. Go to https://kruczki:kruczki@office.altkom.com.pl/
3. Exit Mozilla
Then Mozilla crashes on exit (talkback jumps in, sample talkback IDs:
TB30510019E
TB30509972K
TB30509873K
TB30509795Y
).

I don't see that with yesterday's build (from the 2001-05-14-22-trunk/ dir), so
this is recent.

Ooops, the last one is unrelated, it's a generic 'crash on exit' bug, it also
happens when browsing other sites. I don't see a bug on this though. Should I
open a new one?
This is caused by bug 79779. Right now you get a silent failure when you try to 
load an https site that has a mis-named or untrusted server certificate.

*** This bug has been marked as a duplicate of 79779 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified dupe.
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.