Firebug 1.5 showing 200 Aborted for Ajax requests

Question

When I'm using Firebug 1.5, I'm getting 200 ABORTED errors on certain ajax requests. You can see this happen on this demo page by typing into the textfield. The functionality of the site seems to work just fine even with these errors. Is it safe to simply ignore these errors?

This wicket mailing list thread seems to indicate that the wicket ajax code is doing what it should. Also, this firebug issue seems to indicate there may be some concern. Not sure what to think.

Answer 1

Sounds like aborts on requests that already were coming back with an OK. Firebug will filter these out on some future release, see the code change here:

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

Answer 2

I just spent 30 mins with a similar problem. While this is not an answer directly to the above, a google search for my problem got me here, so I thought I'd add it here in case it saves someone else some time. As always, my problem turned out be developer error. I was binding an ajax request to a submit button, but I'd forgotten to use preventDefault() on the button before making the XHR, so the request was being aborted as soon as the default behaviour for the button kicked in - sometimes before the response came back, sometimes not - but it would always report in firebug 1.5 to be aborted.

Answer 3

I am also encountering this. I can see it on your demo site above on every request, but also I see it on one of my sites. I didn't notice this before, and I am sure I would notice it since I stare at the console for hours everyday. Gives some pretty mixed messages.

I am using a mac with firebug 1.5. This bug has been reported on the firebug bug list id=2712 but seems to be going nowhere. It's a tricky one. I tend to notice it when i have 2 simultaneous requests fired off at the same time, and perhaps one preemptively returns before the other. But this shouldn't cause an Abort message.

Answer 4

I saw your demo page with firebug and seems to be working fine, there is no error to it and note that 200 response denotes that request went successful -> OK, it is not an error abort like you say. Thanks