Firebug causing ignoring of no-cache headers.

[William]

Using FF 3.0.1 and Firebug 1.2.0b13. Firebug is silently causing pages
that should not be cached to hit the cache, causing havoc with my ajax
applications.

Disabling FB and FF3 works properly.

Thank you,
William

[Jason Yates]

Same issue here.

There is a bug report in bugzilla that seems to reference this.

https://bugzilla.mozilla.org/show_bug.cgi?id=441751

[Steven Roussey]

> that should not be cached to hit the cache, causing havoc with my ajax
> applications.

It is good to point out that the bug does require JS -- a simple html
page won't show the error.

[John J Barton]

This is discussed here:
http://code.google.com/p/fbug/issues/detail?id=1029

My sense is that we won't make progress on this until we solve the
double load problem. It looks like the cache issue is not 100%
reproducible and the test cases are complicated (involve login with
different user ids). A very simple test case with detailed steps to
reproduce would increase the chance we can look at this. However the
fix to the double load problem will completely change the way we get
data in Firebug and its likely to fix this problem as well.

[Jason Yates]

The problem exists in 1.2.0b7 and above; downgrading to 1.2.0b6 fixes
the issue for me.

[Steven Roussey]

As an FYI, I think I have narrowed it down to the fact that an AJAX
request is issued to the same URL as the page itself. I think since
they both have the same URL, the cache gets messed up. Such a
technical explanation!

If you login and try to lock or unlock some threads, then hit reload,
it will revert to the state of the page you started at. Hitting shift-
reload will get the expected results. (Note: it is inconsistent the
first couple of times, but after 3 it is 100% consistent). All these
AJAX calls are POSTs to the same URL as the page itself. Adding random
garbage to the URL of the AJAX POST seems to fix the problem (though
completely messes up the expectations of the server side framework we
are using).

Likely, users of PHP PRADO as well as ASP.NET will likely experience
this issue at some point.

[Steven Roussey]

Yep, that was it. Adding random number strings to the callback query
string of the AJAX call eliminated the problem. I was able to
preprocess the URL information on the server side to scrub it out so
the framework I use doesn't see it. All is well with debugging using
Firefox again. Ahh....

-steve--