dhouwn wrote:I can reproduce this on Firefox 4. Two make me wonder:
- Why is NoScript's implementation still active when there's a native one?
It will be removed before Firefox 4 final
dhouwn wrote:
Why is there even an option for ignoring an invalid certificate? I thought it was explicitly mentioned in the spec that the user should not be given an the option on sites using HSTS?
If you're connecting with the site
for the first time, the certificate gets served before any HTTP-level communication can occur, i.e. before the STS header can be seen.
At that stage, you may accept an invalid certificate explicitly, thus making it a valid certificate, which will enable HSTS.
The spec says that
after HSTS is enabled (i.e. the header has been seen first time with a valid, even if made valid by user action, certificate), no chance should be given to user to accept
further invalid certificates.
Are you observing anything different than the above?
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13