Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 57240 - https:// doesn't work under galeon
https:// doesn't work under galeon
Product: Red Hat Linux
Classification: Retired
Component: galeon (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Blizzard
Depends On:
  Show dependency treegraph
Reported: 2001-12-07 13:27 EST by chris
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-12 09:57:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description chris 2001-12-07 13:27:39 EST
Galeon appears not to want to access any sites using the https:// protocol.
 http:// works fine, but whenever I click on a link (or enter a URL
directly in the location entry) which uses https, galeon just silently does
Comment 1 Christopher Blizzard 2001-12-07 17:30:14 EST
Do you have mozilla-psm installed?
Comment 2 chris 2001-12-12 09:57:18 EST
Duh - sorry!  You're quite right: I didn't, but now I do, and now it works. Thanks.

On the subject, though, doing nothing silently isn't a great failure mode. Would
it be possible for Galeon (or Mozilla) to say something slightly more verbose,
so that people like me know that they need to install mozilla-psm?

Thinking about it, why is the SSL support in a separate package anyway? Are
there really people out there who want Mozilla without it?
Thanks again,
Comment 3 Christopher Blizzard 2001-12-12 13:50:43 EST
There are people out there that might not want SSL installed.  Plus, it needs to
be seperate for export control reasons.  I don't know about galeon but there was
a patch checked into Mozilla just in the last day or so that actually says that
SSL isn't installed (finally.)

Note You need to log in before you can comment on or make changes to this bug.