136347 - SSL Not occuring on a secure website

Status: VERIFIED WORKSFORME

(Core Graveyard :: Security: UI, defect, P3)

Description

[David Greenaway]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031104

The web page https://www.namesecure.com:443 does not seem to make a secure
connection with Mozilla, despite the fact that it is prefixed with https and
forms a secure connection in Internet Explorer.

The standard 'unsecure connection' "open padlock" image is displayed at the
bottom right on the taskbar, and no security information is available  on the page.

Actual Results:  No secure connection was made.

Expected Results:  A secure connection of some form with the gray padlock being
"locked" and security information available.

I have not had a chance to intercept data travelling between Mozilla and the
server to see if a actual secure connection is being made, but not being reported.

Comment 1

[Pedro Madeira]

I tried to visit this page with mozilla 0.9.9 2002031115 for linux red hat (rpm
version found on the zilla ftp) and the page actually shows the lock and when
clicked it displays encryption information for that page (128 bit rc4).

So the problem is not general.

Comment 2

[Pedro Madeira]

I am sorry for bothering again but I also tried the mozilla 0.9.9 (latest
milestone release) on windows 2000 professional and the page shows encryption
information ant the lock image is normal for an encrypted page.

So there is no problem here also.

Comment 3

[Sebastian Biallas]

@Reporter: Are you using tabs? If so... do you open the page in another tab than
the first one? (this would be bug 101723)

Comment 4

[Pedro Madeira]

Also no problem on red hat linux mozilla build 2002040814

Comment 5

[Marc Boullet]

Reporter, are you behind a proxy ?
If yes, could it be a dupe of bug #127671 ?

Comment 6

[Mitchell Stoltz (not reading bugmail)]

->PSM

Comment 7

[John Unruh]

Marking works for me.

Comment 8

[John Unruh]

Verified WFM. Reporter, make sure your memory cache is not set to 0.