Closed Bug 141425 Opened 22 years ago Closed 22 years ago

Error connecting HTTPS server on port 81

Categories

(Core Graveyard :: Security: UI, defect)

Other Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

CLOSED WORKSFORME

People

(Reporter: zidek, Assigned: ssaux)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0+) Gecko/20020430 BuildID: 2002043010 I run SSL https server (apache, mod_ssl) on port 81, IE & NN 4.7 works, Mozilla gives error: gts1.westmaster.com recieved a message with incorrect Message Authentification Code .... Reproducible: Always Steps to Reproduce: 1. point mozilla to https://gts1.westmaster.com:81 - diplay error, not page 2. point IE/NN4.7 to same location - will complain about certificate, will display page Actual Results: error will popup in mozilla, in IE/NN you will see page Expected Results: display page maybe some workaround for apache ...
wfm using build 2002043008 on Win2k, certificate warning but pages then load fine.
Assignee: darin → ssaux
Component: Networking: HTTP → Client Library
Product: Browser → PSM
QA Contact: tever → junruh
Version: other → unspecified
*** Bug 141428 has been marked as a duplicate of this bug. ***
wfm with win2k build 20020430.. (i get an certificate error and the page displays)
Worksforme. Reporter, can you try again with a new profile?
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
I checked it again on other system (Windows XP Czech Edition) Mozilla build 2002050106 and it works OK. On my system (Win XP Eng) it doesn't work. Please send me instruction what to do ...
Marking verified. Reporter, if Profile Manager is not available on the windows Start menu, then from a WinXP command line, type "mozilla profilemanager"
Status: RESOLVED → VERIFIED
Ok ! Worksforme winXP different profile, build 2002050106
Works for me, with different profile.
Status: VERIFIED → CLOSED
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.