I believe I have found the solution to my problem... The Nightly
updates after the version (14.0a1 (2012-03-17)), change a default
setting in 'about:config'... This prevents any signature with an MD5 hash
from working at all.<br>
<br>The setting is: security.enable_md5_signatures<br>The default setting of this value in any updates after the one mentioned above, set this to: false<br>In previous version of Nightly, this was set to true by default.<br>
<br>Obviously changing this setting back to 'true' enables the internal websites in question to work again.<br>
<br>Regards,<br><br>James<br><br><br><div class="gmail_quote">On 3 April 2012 18:55, Anthony Hughes <span dir="ltr"><<a href="mailto:ahughes@mozilla.com">ahughes@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Those dates are in line with the last merge (ie. Firefox 13.0a1
-> 14.0a1) so it may be user agent related. Can you try spoofing
your user agent and see if it still works?<br>
<br>
This add-on should help:<br>
<a href="https://addons.mozilla.org/en-US/firefox/addon/user-agent-rg" target="_blank">https://addons.mozilla.org/en-US/firefox/addon/user-agent-rg</a><div><div class="h5"><br>
<br>
On 04/03/2012 03:13 AM, James Renny wrote:
</div></div><blockquote type="cite"><div><div class="h5">Hi,<br>
<br>
I'm running Win7 Enterprise 64bit and use Nightly on a very
regular basis (work and personal)...<br>
<br>
I often access some internal web servers for work and this was
working fine on release 14.0a1 (2012-03-17) and previous releases
but any subsequent releases encounter problems and I cannot access
the site.<br>
The error that appears is a "Secure Connection Failed" error:
(Screenshot below) - This is when attempting to access Cisco
Unified Communications Manager (v6 and v7) Servers web
interfaces. Strangely enough, Cisco Unity Connections Servers Web
Interfaces behave perfectly fine and as expected.<br>
<br>
<img src="" alt=""><br>
<br>
It appears that something was broken in Nightly around March
17th/18th/19th which stopped Nightly from handling the unsigned
certificate from these internal servers.<br>
Normally it would do the usual thing of prompting to add an
exception or if the exception was already present, go direct to
the website.<br>
<br>
I have wiped cookies, history etc etc and the latest versions of
Nightly still bring up this error.<br>
This also happens on a colleagues PC trying to access the same
internal servers. My colleague is also running Win7 Enterprise
64-bit.<br>
<br>
Any advice/help appreciated but feel this is a problem within
Nightly as it was functioning before.<br>
<br>
Thanks,<br>
<br>
James<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Nightly-testers mailing list
<a href="mailto:Nightly-testers@mozilla.org" target="_blank">Nightly-testers@mozilla.org</a>
<a href="https://mail.mozilla.org/listinfo/nightly-testers" target="_blank">https://mail.mozilla.org/listinfo/nightly-testers</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
<pre cols="72">--
Anthony Hughes
Quality Engineer, Mozilla</pre>
</font></span></div>
</blockquote></div><br>