Firebug 1.5 shows 200 interrupts for Ajax requests

Question

When I use Firebug 1.5, I get 200 ABORTED errors for some ajax requests. You can see this on this demo page by entering a text box. The site’s functionality seems to work fine even with these errors. Can I just ignore these errors?

This stream of wicket mailing lists seems to indicate that the kaleidoscope of the ajax code is doing what it needs. Also, this firebug issue indicates there might be some kind of problem. Not sure what to think.

Answer 1

Sounds like an interrupt for requests that have already returned with OK. Firebug will filter them in the next version, see here the code change:

http://code.google.com/p/fbug/source/detail?r=6127

Answer 2

I just spent 30 minutes with a similar problem. Although this is not an answer directly to the above, a Google search on my problem brought me here, so I thought that I would add it here if it would save anyone else. As always, my problem turned out to be a developer error. I linked the ajax request to the submit button, but I forgot to use the preventDefault () function on the button before doing XHR, so the request was interrupted as soon as the button was pressed for the button by default - sometimes it returned before the answer, sometimes not - but it always would report in firebug 1.5 that it be interrupted.

Answer 3

I also come across this. I see this on your demo site above for each request, but also see it on one of my sites. I didn’t notice this before, and I’m sure I would notice it, because every day I look at the console. Gives pretty mixed messages.

I am using mac with firebug 1.5. This error is reported in the error list firebug id = 2712, but it seems that it will not go anywhere. It's complicated. As a rule, I notice this when I have two simultaneous requests at the same time, and perhaps one proactively returns before the other. But this should not cause an error message.

Answer 4

I saw your demo page with firebug and it seems to be working fine, there is no error and notice that the 200 response means the request was successful -> OK, this is not an error, as you say. Thanks