Probably invalid security warning about encryption at




15 years ago
14 years ago


(Reporter: jan.public, Assigned: security-bugs)


Windows XP

Firefox Tracking Flags

(Not tracked)





15 years ago
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040212

When I want to login at my online bank account, I get the warning that:

'Although this page is encrypted, the information you have entered is to be sent
over an unencrypted connection and could easily be read by a third party.'

I got this reply in the mozilla security newsgroup.

The "action" for this form is not https but rather is javascript.
The browser doesn't know (prior to interpreting the javascript)
what the javascript is going to do with the form data, so it assumes
the worst, and you get this warning.  Perhaps the warning should say
"The data from this form is being sent through a script rather than
directly and immediately through secure https, and so I cannot be
sure that the data will be sent securely to the server."

In this case, the javascript appears to me to post the form data
securely to the server.

Communicator 4.x handled this case by waiting to see whether the
subsequent outgoing network connection done by the script was http
or https, and warning only if it was not https.  But mozilla warns
before the script is run, as I understand it.

Reproducible: Always
Steps to Reproduce:
1. Go to the url
2. Fill in a username and password

Actual Results:  
You get a confusing warning.

Expected Results:  
The warning should be as stated above, or no warning should be given at all if
Mozilla can determine that the information is securely transmitted by the java
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.