Closed Bug 79392 Opened 24 years ago Closed 24 years ago

https is not a registered protocol

Categories

(Core Graveyard :: Security: UI, defect)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: wernigm, Assigned: neeti)

Details

(Whiteboard: DUPEME)

any urls https://... result in a popup alert "https is not a registered protocol" (no matter if the target server actually runs port 443 or not). this is build 2001050721 on linux and has only appeared some time (3 weeks?) ago. https worked before that time. some psm component missing? rgds markus
did you install psm? what package did you get, the tar.gz or the installer?
Whiteboard: DUPEME
(not sure if to reply via bugzila) i do a nightly wget http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu.tar.gz and unpack it.
That build should include PSM. Is there a "Privacy and Security" pane in preferences?
there's no "privacy and security" pane in Edit->Preferences. there's Tasks->Privacy and Security.
This means that you don't have PSM at all in that build.... Could you please try getting a new build and making sure that you delete the old one before installing the new one?
deleted old files, installed new, now the browser won't start at all. it just hangs there after registering the plugin 0 for "*".
Let me guess. You untarred as root. And didn't run regxpcom && regchrome as root. And didn't run it once as root. And are trying to run it as a user. If all that's true, please read the installation instructions and release notes more carefully... chrome/component registration involves writing to the install dir and so has to be done by someone with the corresponding permissions. Running it once as root should solve your problem.
Can I send this to PSM? Also, checking Mozilla 0.9 would be a great update.
QA Contact: tever → benc
Dup of bug 75848 or bug 47617?
Markus, are you still seeing this problem with clean installs of recent builds?
no, the problem does not reappear. i realize it was my fault not noticing the install routine had changed. therefore it would make sense to close this bug (i do have other problems with https, but not this one...) sorry for this; i'll pay more attention next time markus
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
-> PSM
Component: Networking → Client Library
Product: Browser → PSM
Version: other → 1.01
Verified fixed.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm1.01 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.