blocks|key|552768|text|我也遇到过类似的问题。在我的例子中，我尝试使用apache服务器%2B+django上的web服务(该服务是我自己编写的)。我有和你一样的输出:+Chrome说它被取消了，而FF做得很好。如果我尝试在浏览器上直接访问服务，而不是ajax，它也会工作。搜索一下，我发现一些较新版本的apache没有在响应头中正确设置响应的长度，所以我手动进行了设置。对于django，我所要做的就是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|552769|response['Content-Length']+=+len(content)|code-block|syntax|javascript|552770|如果您可以控制您尝试访问的服务，请了解如何在您使用的平台中修改响应头，否则您将不得不联系服务提供商来解决此问题。显然，FF和其他许多浏览器都能够正确处理这种情况，但Chrome设计者决定按照规定这样做。|552771|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had a similar problem. In my case, I'm trying to use a web service on a apache server + django (the service was written by myself). I was having the same output as you: Chrome says it was cancelled while FF does it okay. If I tried to access the service directly on the the browser instead of ajax, it would work as well. 
Googling around, I found out that some newer versions of apache weren't setting the length of the response correctly in the response headers, so I did this manually. With django, all I had to do was:

<pre><code>response['Content-Length'] = len(content)
</code></pre>

If you have control over the service you are trying to access, find out how to modify the response header in the platform you are using, otherwise you'd have to contact the service provider to fix this issue. Apparently, FF and many others browsers are able to handle this situation correctly, but Chrome designers decided to do it as specified.

blocks|key|769415|text|如果其他人遇到这种情况，我们遇到的问题是我们从一个链接发出ajax请求，而不是阻止该链接被跟踪。因此，如果您在onclick属性中执行此操作，请确保也使用return+false;。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|769416|entityMap^0|1J|7|25|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

If anyone else runs into this, the issue we had was that we were making the ajax request from a link, and not preventing the link from being followed. So if you are doing this in an <code>onclick</code> attribute, make sure to <code>return false;</code> as well.

blocks|key|769453|text|当我使用http向需要https的url发出请求时，我得到了这个错误。我猜ajax调用没有处理重定向。即使将crossDomain+ajax选项设置为true+(在JQuery+1.5.2上)，情况也是如此。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|769454|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error when making a request using http to a url that required https. I guess the ajax call is not handling the redirection. This is the case even with the crossDomain ajax option set to true (on JQuery 1.5.2).

blocks|key|552897|text|在我的例子中，Apache的mod-rewrite匹配url并将请求重定向到https。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|552898|看看chrome://net-internals/#events中的请求。|552899|它将显示请求的内部日志。检查重定向。|552900|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case, I Apache's mod-rewrite was matching the url and redirecting the request to https. 

Look at the request in chrome://net-internals/#events. 

It will show an internal log of the request. Check for redirects.

blocks|key|552985|text|我也有同样的问题，但在我的例子中，它被证明是一个cookie问题。在后端工作的人更改了我们登录应用程序时设置的JSESSIONID+cookie的路径，我的计算机上有一个使用该名称的旧cookie，但使用的是旧路径。因此，当我尝试登录浏览器(Chrome)时，它向服务器发送了两个名为JSESSIONID的cookie，它们的值不同--这让它感到困惑--所以它取消了请求。从我的电脑上删除cookies修复了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|552986|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem, but in my case it turned out to be a cookie issue. The guys working on the back-end had changed the path of the JSESSIONID cookie that's set when we log in to our app, and I had an old cookie by that name on my computer, but with the old path. So when I tried logging in the browser (Chrome) sent two cookies called JSESSIONID, with different values, to the server - which understandably confused it - so it cancelled the request. Deleting the cookies from my computer fixed it.

blocks|key|769639|text|(使用网页表单ASP.NET)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|769640|我的问题是，我试图从具有服务器端单击事件设置的提交按钮的单击事件中触发Ajax。我必须使按钮只是一个简单的按钮(即<input+type="button">+)|offset|length|style|CODE|769641|entityMap^0|0|1L|L|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

(Using Web Forms ASP.NET)

My issue was I was trying to fire Ajax off the click event of a submit button that had a server side click event setup. I had to make the button just a simple button (i.e. <code>&lt;input type="button"&gt;</code> )

blocks|key|769703|text|如果你使用的是Chrome，你不能在标准的Chrome网络面板中看到足够的信息来确定(canceled)请求的根本原因。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|769704|您需要使用chrome://net-internals/#events，它将显示您正在发送的请求的详细信息-包括隐藏的重定向/有关正在发送的cookies的安全信息等。|769705|例如，下面的代码显示了一个我在网络跟踪中看不到的重定向--这是由于我的cookie没有跨子域发送造成的：|769706|t=1374052796448+[st=++1]+++%2BURL_REQUEST_START_JOB++[dt=261]
++++++++++++++++++++++++++++-->+load_flags+=+143540481+(DO_NOT_SAVE_COOKIES+%7C+DO_NOT_SEND_AUTH_DATA+%7C+DO_NOT_SEND_COOKIES+%7C+ENABLE_LOAD_TIMING+%7C+MAYBE_USER_GESTURE+%7C+REPORT_RAW_HEADERS+%7C+VALIDATE_CACHE+%7C+VERIFY_EV_CERT)
++++++++++++++++++++++++++++-->+method+=+"GET"
++++++++++++++++++++++++++++-->+priority+=+2
++++++++++++++++++++++++++++-->+url+=+"https://...."
...
t=1374052796708+[st=261]++++++++HTTP_TRANSACTION_READ_RESPONSE_HEADERS
++++++++++++++++++++++++++++++++-->+HTTP/1.1+302+Moved+Temporarily
++++++++++++++++++++++++++++++++++++Content-Type:+text/html
++++++++++++++++++++++++++++++++++++Date:+Wed,+17+Jul+2013+09:19:56+GMT
...
t=1374052796709+[st=262]+++++%2BURL_REQUEST_BLOCKED_ON_DELEGATE++[dt=0]
t=1374052796709+[st=262]++++++++CANCELLED
t=1374052796709+[st=262]+++-URL_REQUEST_START_JOB
++++++++++++++++++++++++++++-->+net_error+=+-3+(ERR_ABORTED)|code-block|syntax|javascript|769707|entityMap^0|16|A|0|5|U|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|W|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|X|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

If you're using Chrome you can't see enough information in the standard Chrome networking panel to determine the root cause of a <code>(canceled)</code> request.

You need to use <code>chrome://net-internals/#events</code> which will show you the gory detail of the request you are sending - including hidden redirects / security information about cookies being sent etc.

e.g. the following shows a redirect I wasn't seeing in the network trace - caused by my cookies not being sent cross sub-domain:

<pre><code>t=1374052796448 [st= 1] +URL_REQUEST_START_JOB [dt=261]
 --&gt; load_flags = 143540481 (DO_NOT_SAVE_COOKIES | DO_NOT_SEND_AUTH_DATA | DO_NOT_SEND_COOKIES | ENABLE_LOAD_TIMING | MAYBE_USER_GESTURE | REPORT_RAW_HEADERS | VALIDATE_CACHE | VERIFY_EV_CERT)
 --&gt; method = "GET"
 --&gt; priority = 2
 --&gt; url = "https://...."
...
t=1374052796708 [st=261] HTTP_TRANSACTION_READ_RESPONSE_HEADERS
 --&gt; HTTP/1.1 302 Moved Temporarily
 Content-Type: text/html
 Date: Wed, 17 Jul 2013 09:19:56 GMT
...
t=1374052796709 [st=262] +URL_REQUEST_BLOCKED_ON_DELEGATE [dt=0]
t=1374052796709 [st=262] CANCELLED
t=1374052796709 [st=262] -URL_REQUEST_START_JOB
 --&gt; net_error = -3 (ERR_ABORTED)
</code></pre>

blocks|key|769771|text|我以一种更可怕的方式遇到了这个错误:网络选项卡和chrome://net-internals/#事件在js完成后没有显示请求。当暂停错误callcack中的js时，网络选项卡确实显示请求为(已取消)。在网页中的几个类似请求中，始终只有一个(总是相同的)被调用。重新启动Chrome后，错误没有再次出现！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|769772|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this error in a more spooky way: The network tab and the chrome://net-internals/#events did not show the request after the js was completed. When pausing the js in the error callcack the network tab did show the request as (cancelled). The was consistently called for exactly one (always the same) of several similar requests in a webpage. After restarting Chrome the error did not rise again!

blocks|key|769839|text|我也遇到过类似的问题。使用chrome://net-internals/#events，我能够看到我的问题是由于某种静默重定向造成的。我的get请求是在onload脚本中触发的。url的形式是"http://example.com/inner-path“，301永久地重定向到"/inner-path”。为了解决这个问题，我只是把url改成了“/inner+path”，这样就解决了这个问题。我仍然不知道为什么一周前有效的脚本突然给我带来了问题……希望这能帮助到某人|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|769840|entityMap|0|LINK|mutability|MUTABLE|url|http://example.com/inner-path^0|2P|T|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had a similar issue. Using chrome://net-internals/#events I was able to see that my issue was due to some silent redirect. My get request was being fired in an onload script. The url was of the form, "<a href="http://example.com/inner-path" rel="nofollow">http://example.com/inner-path</a>" and the 301 was permanently redirecting to "/inner-path". To fix the issue I just changed the url to "/inner-path" and that fixed the issue. I still don't know why a script that worked a week ago was suddenly giving me issue... Hope this helps someone

blocks|key|769912|text|我在一个特定的3G网络上遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|769913|在使用chrome://net-internals/#+net_error+=+-101中的事件进行DELETE请求时，总是会失败。|offset|length|style|CODE|769914|其他网络工作得很好，所以我假设有一个故障的代理服务器或什么。|769915|entityMap^0|0|S|G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I had this issue with a particular 3G network. 
It would always fail on DELETE requests with <code>net_error = -101</code> in chrome://net-internals/#events.

Other networks worked just fine so I assume there was a faulty proxy server or something.

blocks|key|769975|text|在我的例子中，它是url中缺失的尾部斜杠。添加尾随斜杠解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|769976|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, it was the missing trailing slash in the url.
Adding the trailing slash solved my problem.

blocks|key|770056|text|我也遇到过同样的问题，对于我来说，我正在创建临时的iframe，并且我在ajax完成之前删除了iframe，这样浏览器就会取消我的ajax请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|770057|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have had the same problem, for me I was creating the iframe for temporary manner and I was removing the iframe before the ajax become completes, so the browser would cancel my ajax request.

blocks|key|770131|text|对于Dropzone.js案例。在我的例子中，这是因为默认情况下timeout+option的值太低。因此，根据您的需要增加它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|770132|{
//+other+dropzone+options
timeout:+60000+*+10,+//+10+minutes
...
}|code-block|syntax|javascript|770133|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dropzonejs.com/#config-timeout^0|W|7|W|E|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

For Dropzone.js case.
In my case it's was caused because of <a href="http://www.dropzonejs.com/#config-timeout" rel="nofollow noreferrer"><code>timeout</code> option</a> value was too low by default. So increase it by your needs.

<pre><code>{
// other dropzone options
timeout: 60000 * 10, // 10 minutes
...
}
</code></pre>

blocks|key|553640|text|扩展@Kazetsukai的答案，如果你正在从点击链接的用户发出AJAX请求，你可能会遇到这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|553641|如果你这样设置你的链接：|553642|<a+href="#"+onclick="soAjax()">click+me!</a>|code-block|syntax|javascript|553643|然后是如下所示的javascript处理程序：|553644|soAjax()+{
++++$.ajax({+...+all+your+lovely+parameters+...+});+++++++
}|553645|要防止浏览器跟随链接并取消任何正在进行的请求，您应该添加return+false或e.preventDefault()以停止传播单击事件：|offset|length|style|CODE|553646|soAjax()+{
+++$.ajax({+...+etc+...+});
+++return+false;
}|553647|或者：|553648|soAjax(e)+{
+++$.ajax({+...+etc+...+});
+++e.preventDefault();
}|553649|entityMap^0|0|0|0|0|0|S|C|15|I|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|15|8|@$O|16|P|17|Q|R]|$O|18|P|19|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

Expanding on @Kazetsukai's answer, you may run into this problem if you are making your AJAX request from the user clicking on a link.

If you set up your link like so:

<pre><code>&lt;a href="#" onclick="soAjax()"&gt;click me!&lt;/a&gt;
</code></pre>

And then a javascript handler like the following:

<pre><code>soAjax() {
 $.ajax({ ... all your lovely parameters ... }); 
}
</code></pre>

To prevent your browser from following the link and cancelling any requests in progress, you should add <code>return false</code> or <code>e.preventDefault()</code> to stop the click event from propagating:

<pre><code>soAjax() {
 $.ajax({ ... etc ... });
 return false;
}
</code></pre>

Or:

<pre><code>soAjax(e) {
 $.ajax({ ... etc ... });
 e.preventDefault();
}
</code></pre>

blocks|key|770267|text|检查页面是否重新加载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|770268|问题：|770269|在我的例子中，在触发Ajax之前，我是在点击事件中使用location.reload()重新加载页面的。此外，还有第二次Ajax调用取得了成功。|offset|length|style|CODE|770270|解决方案：|770271|我删除了reload，并将其放入上一次Ajax调用的成功回调中，它起作用了。|770272|entityMap^0|0|0|R|H|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

<h3>Check for page reloads.</h3>
Problem:
In my case I was reloading the page using <code>location.reload()</code> inside click event, before Ajax being fired.
Also, there was second Ajax call in the success.
Solution:
I removed the the reload and put it inside success callback of last Ajax call and it worked.

I am trying to hook up a script to Microsoft's World-Wide Telescope app. The latter listens on port 5050 for commands. It is running on the same machine as the browser (Chrome right now, but as far as I can tell the behavior is the same with Firefox 7 and IE 9).

I am sending a "Access-Control-Allow-Origin: *" header with the original html file to try to eliminate XSS restrictions as my problem.

My code to access WWT is as follows:

<pre><code>$.ajax({
 type: 'POST',
 url: url,
 data: data,
 crossDomain: true,
 success: success,
 dataType: dataType
});
</code></pre>

url in this case is "http://127.0.0.1:5050/layerApi.aspx?cmd=new&amp;..." (obviously ... is shorthand here for some additional parameters).

Looking at the network diagnostics in Chrome, I can see this:

<pre><code>Request URL:http://127.0.0.1:5050/layerApi.aspx?cmd=new&amp;...
Request Headersview source
Accept:application/xml, text/xml, */*; q=0.01
Content-Type:application/x-www-form-urlencoded
Origin:http://gwheeler4
Referer:http://gwheeler4/conceptconnect.html
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1
</code></pre>

The request is going out - I see WWT make a new layer. However, I don't get a callback. If I add an error callback that gets called, but the error property on the jqXHR object is just "error" and status is 0. If I look at the network request in Chrome I see "(cancelled)" as the status and no response.

If I take that same URL and paste it in a new browser tab, I can see that the response is the expected XML.

Of course, a difference here is that this is a GET not a POST, but I've tried that in my script and it makes no difference.

I'm pretty stumped by this and would appreciate any fresh ideas.

jQuery Ajax requests are getting cancelled without being sent

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在尝试将脚本连接到Microsoft的World-Wide Telescope应用程序。后者监听端口5050上的命令。它和浏览器运行在同一台机器上(Chrome现在，但据我所知，它的行为与Firefox7和IE9是一样的)。我在原始html文件中发送了一个"Access-Control-Allow-Origin：*...

问jQuery Ajax请求未发送就被取消
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问jQuery Ajax请求未发送就被取消EN