if you think its a bug, File a Bug on Bugzilla, create an account and File:

• https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox

Thanks, Swarnava. I have submitted it as a bug.

For others reading this my thoughts would be:

I wonder if it in fact should be investigated as being a problem with your website ? Are you the website designer ?

If you do have questions about website design

1. first of all verify the code is valid using the W3 validator http://validator.w3.org/unicorn/
   • and of course that the site is designed and intended to work with Firefox 12
2. consider asking for advice on the Mozillazine forum http://forums.mozillazine.org/viewforum.php?f=25

In fact I note you mention you did file a bug and I assume that is:

• Bug 749098 - cannot log in to website with Firefox v. 12.0
  and is currently receiving attention.

I am a developer on this project. This is a large web application using the Extjs javascript library, with a Java backend. We have been working on this for a couple of years at least, and we have developed it specifically to work in Firefox and Chrome. These are the browsers we recommend to our users (linguistics researchers from around the world).

Suddenly, with Firefox v. 12, one can no longer log in. After logging in with Firefox, one bounces directly back to the log in page. In Chrome or Opera (or with all previous versions of Firefox), one proceeds after login to the web application.

Yes, I did file it as a bug, and you are correct, it is "Bug 749098 - cannot log in to website with Firefox v. 12.0". The developers have isolated the problem. They are in the process of deciding whether it is an issue they will handle in a new release, or whether it is a problem that needs to be fixed in Extjs 3.31.

I have edited our /modules/basex/ext-basex.js code according to the suggestion of one of the Mozilla developers who worked on the bug I posted.

Source File: http://hudesktopdevel.hucompute.org/modules/basex/ext-basex.js Line: 1010 > ('timeout' in r) && (r.timeout = callback.timeout); It should be something like: options.async && ('timeout' in r) && (r.timeout = callback.timeout);

This has solved our problem! Login now works from Firefox 12, and it continues to work in other browsers. Perhaps this can be the suggested fix for Extjs 3 users who have login problems with Firefox 12.

I have an application developed in Zend Framework. I have the same log-in issue in my site after i upgraded my browser to FF12.0. It was working fine in all browsers even in FF 11.0 previously. But now some of my site users who are using FF12 are no longer able to log-in to the site(they redirected back to log-in page).

I have downloaded web developer toolbar addon in my firefox and disable the cache using this addon and now i am able to successfully log-in in my site. But definitely it's difficult for end users to do it(Because these adons are meaningful for developers or technical person).

This is strange that @excyberlabber the issue that you mentioned in you post is related to extjs. At the same time this issue arises with zend framework as well...How to find out the issue with Zend that causes conflicts with FF12??

The problem in Extjs is that the javascript uses something called XHR (in javascript new XMLHttpRequest() ) and a timeout together:

"Adds standard HTTP Auth cache support to every request (XHR userId, password config options)"

The new Firefox 12 browser does not allow this, because something in the standard does not allow it. Look in your Zend code for the way that the request is handled in the javascript, and look for a timeout command...

I don't know exactly why the options.async makes all the difference, but that is what makes ours work. Maybe someone can help explain this better.