Firebug 1.5 显示 200 Ajax 请求已中止
当我使用 Firebug 1.5 时，我在某些 ajax 请求上收到 200 ABORTED 错误。您可以通过在文本字段中输入内容来在此演示页面上看到这种情况发生。即使存在这些错误，该网站的功能似乎也能正常工作。忽略这些错误是否安全？
这个 wicket 邮件列表线程 似乎表明 wicket ajax代码正在做它应该做的事情。此外，这个 firebug 问题似乎表明可能存在一些问题。不知道该怎么想。
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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我刚刚花了30分钟解决类似的问题。虽然这不是上述问题的直接答案，但对我的问题的谷歌搜索让我来到了这里，所以我想我应该将它添加到这里，以防它节省其他人的时间。一如既往，我的问题是开发人员的错误。我将 ajax 请求绑定到提交按钮，但在制作 XHR 之前我忘记在按钮上使用 PreventDefault()，因此一旦按钮的默认行为启动，请求就会被中止 - 有时在响应返回，有时没有 - 但它总是会在 firebug 1.5 中报告被中止。
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.
我也遇到这个情况。对于每个请求，我都可以在上面的演示网站上看到它，而且我也在我的一个网站上看到它。我以前没有注意到这一点，而且我确信我会注意到这一点，因为我每天都会盯着控制台几个小时。给出了一些相当复杂的信息。
我使用的是装有 firebug 1.5 的 Mac。该错误已在 firebug bug 列表 id=2712 上报告，但似乎无处可去。这是一个棘手的问题。当我同时发出 2 个并发请求时，我倾向于注意到这一点，并且也许其中一个请求先于另一个请求先返回。但这不应该导致中止消息。
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.
听起来像是中止已经返回 OK 的请求。 Firebug 将在未来的版本中过滤掉这些内容，请参阅此处的代码更改：
http://code.google.com/p/fbug/source/detail?r=6127
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
我使用 Firebug 看到了您的演示页面，似乎工作正常，没有错误，并注意 200 响应表示请求成功。这不是像你说的那样错误中止。
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 was successful. It is not an error abort like you say.