Firefox Sync does not work no more neither.

I had the same problems and rolled back to beta11 which runs fine with https behind a corporate proxy.

We already had the same problem withe Beta5. I wonder what kind of testing they are doing to avoid repeating such bugs!

I think sync doesn't work because it needs a https conection as well - which doesn't work anymore.....

Proxy server : squid/2.6.STABLE19 OS: WinXP SP3 Server requires authorization : NTLM When I've try to access to secure web site (https), I've get "The proxy server is refusing connections". There is only "TCP_DENIED/407 1724 CONNECT www.google.com:443 - NONE/- text/html" in proxy log file.

Same time, from IE, https open sites via same proxy without any problems.

Works fine with previous beta and ff 3.6 too

Hello all ...

... our Proxy Server (Squid) requires NTLM authentication and allows fallback to basic authentication ... with Firefox 4 Beta 12, HTTP works using NTLM authentication as usual but HTTPS fails: it falls back to basic authentication (you get an authentication popup).

- This Problem did not exist in Firefox 4 Beta 11. - Firefox 4 Beta 5 had a similar problem.

Looks like nobody tests Firefox in Enterprise/Proxy/Single Sign On Environments. Aside from that, there are in my opinion some other limitations which make Firefox in Enterprise Environments a pain. (no MSI installer, Updater is a pain, no Group Policy Support, does not use Sandbox features in Vista an higher as do Chrome and IE, Plugin Container made Firefox crash less - but buggy Plugins still crash Firefox, ...)

As i said, just my opinion. But i hope/think this Proxy/NTLM/HTTPS Authentication Problem will be fixed soon.

The Firefox developers who are looking at this need a little more information to find the best fix.

In particular, we need the following:

• What https sites don't work? Does https://addons.mozilla.com work? Does sync work? How about paypal?
• More information about the proxy server you're using. There are unfortunately dozens of different server configs/certs out there and while we DO have testing for some cases, it's not all of them.
• We also need people to test try builds (that is builds where we attempted to fix the problem) to see if it fixes it for you.

If you're willing to have one of our developers contact you via email just say so here. Since I'm an admin for this site, I can look up your email address and pass it to the devs. Please don't post your email address publicly.

Hello Cww,

i´m absolutely willing to test and help getting this issue fixed.

Please tell my E-Mail Address to the developers. I´m looking forward to hearing from them.

...

Proxy Server: Squid 2.7.STABLE7-1ubuntu12 running on Ubuntu 10.04.02 LTS 64-bit

Our Squid is configured to first ask for ntlm authentication, if that fails it falls back to basic authentication.

For me it looks like every https site does not work -> i get an authentication popup, which is the basic authentication i mentioned. When i enter the correct credentials, then the https site works, so it´s clearly an issue regarding https and ntlm authentication. http sites work correclty using ntlm authentication -> no authentication popups.

p.s.: i´m just heading out of the office, so my reply may take until tomorrow ...

kind regards / John Kirk

This "question" is duplicated here: http://support.mozilla.com/sr-LATN/questions/787429

Hi,

I try to answer your questions:

What https sites don't work? Does https://addons.mozilla.com work? Does sync work? How about paypal?

Not a single https site is working

More information about the proxy server you're using. There are unfortunately dozens of different server configs/certs out there and while we DO have testing for some cases, it's not all of them.

Our proxy is from astaro. If you can tell me a tool for getting more information I could send you the results.

We also need people to test try builds (that is builds where we attempted to fix the problem) to see if it fixes it for you.

No problem send me a link and I can tell you the results.

As far as I know you use subversion for version control. The proxy problem was fixed after beta5 and came back with beta11. It shouldn't be such a big problem to see what fixed the problem and what broke it again?

Problem is solved in nightly build (4.0b13pre 2011-03-02) from today!

FTR, there are about 600+ fixes that go into every beta so it's not super easy to bisect out the change that caused it.

As far as I can tell, they seem to think that there are 2-3 different problems with the same/very similar symptoms, all involving proxies. They think they've fixed them all for RC1.

I've passed along the email addresses but right now, it looks like we just want people to test an early build. I'll have a link for you as soon as it's built.

Build is out:

http://ftp.mozilla.org/pub/mozilla.or.../firefox-4.0b13pre.en-US.win32.installer.exe

Install that somewhere (not in your current install directory), quit all open Firefox instances and try it. Let me know if it works.

Solved with this nightly

I can also confirm that this problem is solved with this nightly build.

thanks & kind regards, John Kirk

I confirm that this problem seems to be fixed. Thanks.

Problem seems to be still solved in the nightly build 4.0b13pre 2011-03-03 :-)

This problem is back with FireFox 7.0.1.