以我为例，我发现它是jquery的全局超时设置，一个jquery插件设置全局超时为500ms，这样当请求超过500ms时，chrome就会取消请求。

在这能帮助任何人，我遇到取消状态时，我省略了返回false;在表单中提交。这导致ajax发送之后立即紧跟提交操作，这将覆盖当前页面。代码如下所示，在末尾返回重要的false。

$('form').submit(function() {

    $.validator.unobtrusive.parse($('form'));
    var data = $('form').serialize();
    data.__RequestVerificationToken = $('input[name=__RequestVerificationToken]').val();

    if ($('form').valid()) {
        $.ajax({
            url: this.action,
            type: 'POST',
            data: data,
            success: submitSuccess,
            fail: submitFailed
        });
    }
    return false;       //needed to stop default form submit action
});

希望这能帮助到别人。

从严格的Angular角度来看:

当你不能在代码层面上正确地中断时，就会发生这种情况。

假设request1出来了，它的响应也是， 在那之后，嵌套的request2也出去了，它的响应也来了，我们直接打破了循环，没有正确地破坏request1的订阅，

在那个时候，它发生了

我也遇到过同样的问题，在我们的代码深处，我们有这样的伪代码:

创建iframe 加载iframe提交一个表单 2秒后，移除iframe

thus, when the server takes more than 2 seconds to respond the iframe to which the server was writing the response to, was removed, but the response was still to be written , but there was no iframe to write , thus chrome cancelled the request, thus to avoid this I made sure that the iframe is removed only after the response is over, or you can change the target to "_blank". Thus one of the reason is: when the resource(iframe in my case) that you are writing something in, is removed or deleted before you stop writing to it, the request will be cancelled

I had the same issue when updating a record. Inside the save() i was prepping the rawdata taken from the form to match the database format (doing a lot of mapping of enums values, etc), and this intermittently cancels the put request. i resolved it by taking out the data prepping from the save() and creating a dedicated dataPrep() method out of it. I turned this dataPrep into async and await all the memory intensive data conversion. I then return the prepped data to the save() method that i could use in the http put client. I made sure i await on dataPrep() before calling the put method:

等待dataToUpdate =等待dataPrep(); http。把(apiUrl dataToUpdate);

这解决了间歇性取消请求的问题。

请求可能已经被跟踪保护插件阻止了。