Closed
Bug 75848
Opened 24 years ago
Closed 24 years ago
https protocol not recognized
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: tommybee99, Assigned: ddrinan0264)
References
Details
(Keywords: smoketest)
Attachments
(4 files)
MAJOR bug -- when I try to load an https site directly, I get a dialog box that
states "https protocol not recognized." When I try to load one indirectly via a
link, it fails to do anything. Build 2001041212. I've restarted the computer but
that didn't change anything.
Comment 1•24 years ago
|
||
Reporter:
Please include in all Bugs the build ID !
| Reporter | ||
Comment 2•24 years ago
|
||
Uh... was "Build 2001041212" not enough?
Comment 3•24 years ago
|
||
I'm so tempted to write a comment in this bug but i'll refrain.
Comment 4•24 years ago
|
||
It's broken for me too, Build 2001041212/NT4.
Going to a https URL launches Communicator 4.76 as a helper app.
Completely busted for mailnews.
Can we get platform/OS set to all if anybody spots it on Linux?
Comment 5•24 years ago
|
||
You need to provide a URL that does not work.
It is WFM at https://selfpage.dion.ne.jp/cgi-bin/cust/daa_jikan_lst.cgi and at
the support page of www.earthlink.net,
but I can not launch PSM, and am unable to confirm the security status.
2001041212 Mac trunk
Comment 6•24 years ago
|
||
Tested URLs:
https://www.fortify.net/sslcheck.html (launches 4.x)
http://webmail.telstra.com (reditects to secure site, launches 4.x)
http://www.hotmail.com (does nothing)
https://www.thawte.com
https://selfpage.dion.ne.jp/cgi-bin/cust/daa_jikan_lst.cgi
It's definately broken here...
Comment 7•24 years ago
|
||
There is a possibility that those sites are not TLS-capable.
You should try to uncheck "Enable TLS" under Preferences|Privacy/Security|SSL
and see if it makes difference.
| Reporter | ||
Comment 8•24 years ago
|
||
Comment 9•24 years ago
|
||
->Crypto
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: ckritzer → junruh
Comment 10•24 years ago
|
||
It's the same problem under Linux.
| Reporter | ||
Comment 11•24 years ago
|
||
Build 2001041308 from MacMozillaFullInstaller.sea.bin will not load https URLs,
but the same build from mozilla-mac-trunk.sea.bin will. I prefer using the
Installer, and I have a feeling that others do as well.
Comment 12•24 years ago
|
||
recommend changing Platform and OS to all as this appears to be accros the
board on a wide range from Linux to Win32, to MacOS. recommend marking bug
76026 a dupe of this as it probably covers the same ground this bug already
does.
Comment 13•24 years ago
|
||
Confirming on 2001041408 Win2k, changing Platform/OS=All and adding Smoketest keyword (visiting a https site is part of the smoketests).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: smoketest
OS: Mac System 9.x → All
Hardware: Macintosh → All
Comment 15•24 years ago
|
||
I'm using build 2001041408 and it works for me on Win2K. I did just delete my
profile and the mozregistry.dat file. I've got SSL2, SSL3 and TLS enabled. All
of the sites mentioned in this bug work perfectly for me.
Comment 16•24 years ago
|
||
After deleting mozregistry.dat and using a fresh profile, this still does not work for me (2001041408 Win2k installer).
Comment 17•24 years ago
|
||
fixed in win32-installer as of 2001041520 build. A couple of checkins
concerning PSM happened, must have straightened out the mess, atleast on win32.
As a side note, I know PSM2 isnt finished, but 2 things seemed muddled now, a
logoff dialog box is looking bad, and the prefs panel for Privacy/Security is
also looking bad. I'll attach a couple images to demonstrate what I mean.
Comment 18•24 years ago
|
||
Comment 19•24 years ago
|
||
Comment 20•24 years ago
|
||
| Reporter | ||
Comment 21•24 years ago
|
||
https worksforme now on build 2001041604 (installer) on Mac OS 9.1 -- the site
that was not working for me, Yahoo! mail, is now functioning properly.
Comment 22•24 years ago
|
||
Resolve this as worksforme per bug reporter.
Bugs having to do with dialogs should be filed separately (if not already filed).
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 23•24 years ago
|
||
*** Bug 76023 has been marked as a duplicate of this bug. ***
Comment 24•24 years ago
|
||
*** Bug 76026 has been marked as a duplicate of this bug. ***
Comment 26•24 years ago
|
||
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Comment 27•24 years ago
|
||
Mass changing Security:Crypto to PSM
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•