What does RED text mean in the Firebug net tab?

Question

I can't seem to find any help on this but under the NET tab in Firebug one of my sites is showing red highlighted items. Unfortunately the site is protected right now so I can't posted the link.

Can anyone answer what this means?

(image here) http://imgur.com/hueWT.gif

Answer 1

Ordinarily it indicates a 404 error or some other error, but here you have a 200 status. Use the plus button to expand and look at the response headers. What do they say?

Edit: I checked the Firebug source. It definitely means their was a response header in the 400 or 500 range.

Why do you have a 200 OK header, also? I couldn't tell you. I can say that it's based on more than just the response headers looking at the logic in FB. However, I'm not that familiar with it (first time that I've looked at firebug's source).

If you're very curious about the red AND the 200 OK, check out what you have under the plus button. If that doesn't answer your question (do you have a page but maybe it's a 404 page?), fire up a packet sniffer to see in full detail what happens after the initial error header.

Answer 2

Hi,

I found this Link today morning from dzone. I think this will explain the net tab in firebug.

Answer 3

I'm also getting a 200 OK in red. What I'm doing is I'm calling a function from a different domain using a script (RPC handler) from another domain. Any clues?

Answer 4

There is some error (usually 404 - the resouce cannot be found), however, your browser might be picking them up from somewhere else, like the cache on your proxy?

[edit] Turns out this is probably a bug

Answer 5

This also happens when your request is stopped.

It is a common issue with Firefox when you want to send an Ajax request on ESC key press.

To avoid this problem, you can add a small delay:

  function callOnEscPress(e){
    if (e.keyCode == Event.KEY_ESC){
      setTimeout(function(){new Ajax.Request(*your_params*)},100);
      Event.stopObserving(document,'keydown', callOnEscPress);
    }
  }
  Event.observe(document,'keydown', callOnEscPress)

Answer 6

I had this same issue today. The response came back 200 (ok), but not the data. The same request worked in IE after displaying a security pop up (site is accessing information which is not under its control), so I guess it could be cross-domain scripting related.