I still have the same issue with beta 6. The patch has not landed in the new beta?

This is still not working with beta 6. I hope this will be fixed before the release or it will be the end of Firefox for me.

I just tested with FF Beta 6 release candidate build 2 and this still appears to be an issue. Connecting to Internet on corporate network via Squid proxy.

The fix for this will be in beta 7.

Beta 6 is an emergency release to fix an issue that was causing beta 5 to crash. It does not include the fixes that were originally planned for beta 6, they have been pushed back to beta 7, which is still planned for late September.

I wish I would have read this before updating again :D

Guess I'll wait until beta 7

Same here, using FF4.0b6 (Mozilla/5.0 (Windows NT 5.2; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6), switching to private mode allows me to access https sites.

I'm behind a squid/2.6.STABLE21 proxy server, NTLM authentication.

in normal mode I see:

HTTP/1.1 CONNECT support.mozilla.com:443 --->

<--- HTTP/1.0 407 Proxy Authentication Required

The browser does not attempt to continue the handshake.

In private mode I see:

HTTP/1.1 CONNECT support.mozilla.com:443 --->

<--- HTTP/1.0 407 Proxy Authentication Required

HTTP/1.1 CONNECT support.mozilla.com:443, NTLMSSP_NEGOTIATE -->

<--- HTTP/1.0 407 Proxy Authentication Required, NTLMSSP_CHALLENGE

HTTP/1.1 CONNECT support.mozilla.com:443 NTLMSSP_AUTH -->

<--- HTTP/1.0 200 Connection established

Sorry to report that I noticed this issue when going from beta 5 to beta 6 in my office but it might have been present already in 5 I suppose! Best example: unable to access Firefox extensions :-)

Workaround: install a local proxy (e.g. CNTLM) and use this proxy in FF then configure your local proxy to talk to the company one. CNTLM support NTLM auth!

This will be fixed in beta 7.

I had the same problem browsing HTTPS sites and below fix worked for me - 1. Tools - > Options -> setup manual proxy configurations. 2. Check "Use this proxy server for all protocols"

I had the same problem browsing HTTPS sites and below fix worked for me - 1. Tools - > Options -> setup manual proxy configurations. 2. Check "Use this proxy server for all protocols"

I had the same issue with HTTPS sites and below simple fix worked for me.

1. Configure Manual PROXY setting through Tools -> Options -> Advanced Tab -> Network -> Connection -> Settings 2. Check "Use this proxy server for all protocols"

I had same issues with HTTPS site and below work around fix worked for me.

1. Configure Manual Proxy Settings. 2. Check "Use this proxy server for all protocols"

@fox123, I have always had those options checked and it still won't work behind our NTLM proxy. I even tried installing the update and changing the settings, just to be sure. Still doesn't work.

This issue seems fixed in FF beta 7 but only partially: surfing HTTPS sites is ok but if I used logmein, the final connection step will end up with an error 11004 (which is related to DNS somehow) and failed.

It does work with FF 3.6 and IE so FF4 IS the culprit. I wonder if https is not handled properly between FF and the plugin.

PS at home no issue

I have this problem with FF 4.0 release, not beta.