575198 - Firefox can't block the redirect from a encrypted page to a non-encrypted page

Status: RESOLVED INCOMPLETE

(Firefox :: Security, defect)

Description

[gddream]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6

When we will leave an encrypted page (such as a page with SSL), Firefox can popup a dialog to give the alert, but can't block this action, so that some private information may be transport over the Internet without encrypte.

In situation below, our inputs will submit through the URL with non-encrypted connection, and it may be cought by others. So I want to Firefox to add a button in the alert dialog which allows users to block these redirection and protect the private information.

I know Firefox can block the ordinary redirect, but I think it is necessary to add a button in this alert dialog

Reproducible: Always

Steps to Reproduce:
1. Go to https://encrypted.google.com/
2. Click "Search settings" to change the language from English to Chinese(Simplified), then save it.
3. Input something (such as "firefox") then press enter, the result will come out.
4. Put the input focus into the input box, beats the Enter rapidly, then a dialog will popup and show that we will leave a encrypted page.
Actual Results:  
a dialog will popup and show that we will leave a encrypted page, but we still can't block the redirect.

Expected Results:  
a dialog will popup and show that we will leave a encrypted page, but we still can't block the redirect.

Comment 1

[Parker]

Tested on Nightly 54.0a1 (2017-02-27) (64-bit) and could not recreate the issue

Comment 2

[Firefox Bug Husbandry Bot]

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.