Closed Bug 103699 Opened 24 years ago Closed 24 years ago

Browser just won't navigate to https:// links

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: brendan.reville, Assigned: asa)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010917 BuildID: 20010917 I just installed the latest version of Mozilla, and whenever I navigate to a secure link (https:// style) it just does nothing at all. This happens when I'm submitting a form to an https link, when I'm redirected to one, and simply when I try to visit one. It's very strange behaviour. Reproducible: Always Steps to Reproduce: 1. Take Mandrake 8.1 2. Install the Mozilla RPMs for 0.9.4 onto there (to replace the existing mozilla 0.9.3).. using --nodeps and --replacefiles. 3. Try visiting a site with a https:// URL. Actual Results: Nothing happens Expected Results: It should have navigated to the site.
Did you install the Personal Security Manager, PSM? The redhat version begins with mozilla-psm-* I assume Mandrake packagers follow the same structure.
invalid. https requires PSM. please install the PSM rpm.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Yes, it required psm. But surely it should give some kind of end-user notification rather than just hanging. Does the website give any information about psm being a required download? I didn't know it existed until I hit the ftp site.
This is actually a dup of bug 47617, "Connection to https needs to tell user to install PSM if w/o".
Not a dup. The summary here reads "Browser just won't navigate to https:// links" A fix for bug 47617 would likely cause prevent that bugs like this were filed in the first place, but it's not a dup as such. There are ...trunkloads of these scattered around in Bugzilla, so a fix for 47617 would be a good thing. The issue is now in the 0.9.5 release notes.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.