Bug 87706

Summary: Superfluous security warning when going from https to https in a new window
Product: [Retired] Red Hat Linux Reporter: David Balažic <david.balazic>
Component: mozillaAssignee: Christopher Blizzard <blizzard>
Status: CLOSED WONTFIX QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-16 21:18:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Balažic 2003-04-01 16:34:47 UTC
Description of problem:

Mozilla gives a warning dialog when I click I open a link in a new window or new
tab, where both the original page and the newly opened one are secure ( https )
and from the same server.

The dialog show is :

Security Warning

You have requested an encrypted page. The web site has identified itself
correctly, and information you see or enter on this page can't easily be read by
third party.

 [ ] Alert me whenever I am about to view an encrypted page.

            [ OK ]

This is needless and annoying. This dialog should be only displayed when going
from unsecure to secure pages. And maybe when going from one secure site to another.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. visit a secure site, like https://bugzilla.redhat.com/bugzilla/index.cgi
2. right click on any link that points to another page on the same site, like
https://bugzilla.redhat.com/bugzilla/redhat-faq.cgi ( the "Help" link at the
bottom ), and select "Open Link in New Window" or "Open Link in New Tab", you
can also middle click
Actual results:

security warning dialog appears

Expected results:

no dialog

Additional info:

Comment 1 Christopher Blizzard 2003-04-16 21:18:10 UTC
If this gets fixed upstream, I'll take it but I'm not going to spend time on it.