Closed Bug 105106 Opened 23 years ago Closed 23 years ago

https URL's ignored

Categories

(SeaMonkey :: Build Config, defect)

Product:
SeaMonkey
Component:
Build Config
Platform:
Sun
SunOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: dem, Assigned: leaf)

References

(
URL
)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.5) Gecko/20011013
BuildID:    2001101312

Mozilla will not load any URL starting with https://.
It just sits there.
It doesn't matter if the URL is manually entered or referenced
by a link.


Reproducible: Always
Steps to Reproduce:
1. Manually enter any known URL which starts with https://.
2.
3.

Actual Results:  Nothing happens.


Expected Results:  Mozilla should have loaded the page.


Perhaps this is just with the Solaris 8 build.
Version 0.9.4 didn't have this problem.
Proxies are in use.
Did you make sure to install the Personal Security Manager?
I just installed the tar file I downloaded from mozilla.org.
I didn't install anything extra, nor did I for 0.9.3 or 0.9.4.

I though of another potential difference between how I installed 0.9.4 and 0.9.5.

The software is installed in a common directory.  Prior to 0.9.5, I would first
install the software under my own UID and run it once to get everything
registered, then chown the files to root.

With 0.9.5, I chown'd the files to root first, then ran the script specified in
the Release Notes as root.

Perhaps the script left out a key step.

Please ignore my last comment.  I redid the 0.9.5 installation as I had
previously installed mozilla, without using the Release Notes script, and still
have the problem.

I can confirm this for build 2001101312.  When running this build under Solaris
7 (even though its a Solaris build :)) https sites don't work.  The easy work
around is too use nighlt builds - i.e. build 200110511 - PSM has worked
continuously with nightly builds for at least a couple of months.

It looks like for some reason crypto was not enabled for the 0.9.5 milestone for
Solaris.  When I compared the libs in the mozilla dir for the 0.9.5 tar ball and
the 200110511 build, the 0.9.5 build was missing 3 libs - libfreebl_hybrid_3.so,
libfreebl_pure32_3.so, and libnssckbi.so - while the 200110511 build was missing
1 - libxlibrgb.so.  If I'm not mistaken the https functions are in libnssckbi.so
(NSS = Netscape Security Something?).

Anyway, to me it looks like someone just needs to rebuild the milestone for Solaris.
Status: UNCONFIRMED → NEW
Ever confirmed: true
ccing asa.  Asa, who handles this stuff?
I also noticed this problem today when I upgraded to
0.9.5 from 0.9.4.  It doesn't matter if you're going
through proxy or using direct connection; secure http
links are ignored with Mozilla 0.9.5 binaries for Solaris.
I also have this problem on Linux with 0.9.5.  It's been present since at least
2001101108, but was not present in 0.9.4.

I just tried installing with Personal Security Manager, and now the problem
is gone.

If this is the intended behavior, Mozilla should both:
  - *Tell* the user that not installing PSM will disable https links  - when an
https link is attempted, show a page explaining why it will not
    work

It is not clear to me that this *is* the intended behavior, since https links
worked with 0.9.3 and 0.9.4 without having to install PSM.
darin

*** This bug has been marked as a duplicate of 47617 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
I'm pretty sure the original problem mentioned here - no https support in Sparc
Solaris 0.9.5 milestone build - is not a duplicate of bug 47617.

Bug 47617 (and its many duplicates and the comments by Scott McPeak on this bug)
seem to be caused by people installing mozilla using the installer and choosing
not to install the PSM. This causes https not to work.

This Solaris bug is different.  There is no Solaris installer AFAIK. This bug
deals seems to be caused by the 0.9.5 Solaris tar ball being built without PSM
support, as evidenced by the fact that there is no libnssckbi.so in the tar ball
(http://ftp.mozilla.org/pub/mozilla/releases/mozilla0.9.5/mozilla-sparc-sun-solaris2.8-0.9.5.tar.gz)
 . That file exists in the nightly builds and in the 0.9.5 Solaris tar ball, and
https work fine in those cases.  Also, libnssckbi.so is present in both the
0.9.5 and 0.9.4 Linux milestone tar balls for which PSM works fine.

Anyway, if I'm mistaken about this, please explain to me where libnssckbi.so
went ;).
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
leaf: who is responsible for the solaris build?
it's a group-raised baby; which means there isn't *one* person responsible, but
i will take responsibility and attach a change to the build automation to turn
on psm for solaris builds.
Assignee: neeti → leaf
Status: REOPENED → NEW
Component: Networking → Build Config
QA Contact: benc → granrose
ah. here's the problem:
Joerg Rieger <Joerg.Rieger@informatik.med.uni-giessen.de>, Sparc Solaris 2.8

built the solaris 2.8 binary... he probably did not enable psm. Since this is a
contributed build, i don't really have the power to force him to respin it for
crypto. i'd reassign the bug to him, but he doesn't have a bugzilla account.

I'm going to mark this wontfix, but i will send him mail and ask him to respin
with crypto.
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WONTFIX
*** Bug 108143 has been marked as a duplicate of this bug. ***
*** Bug 111360 has been marked as a duplicate of this bug. ***
*** Bug 112124 has been marked as a duplicate of this bug. ***
verified wontfix
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.