blocks|key|1205641|text|如果请求是由插件生成的，ajax响应的内容还不可见。这个问题有可能很快就会得到解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1205642|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|$]]

The content of ajax responses is not visible yet if the request is generated by a plugin.
There is some chance that this problem will be fixed soon.

blocks|key|991252|text|如果你正在使用Google+Chrome的开发频道：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|991253|http://www.chromium.org/getting-involved/dev-channel|offset|length|991254|...you应该能够在开发人员工具控制台中右键单击，然后单击"Enable+XMLHttpRequest+logging“。|991255|启用后，您将在控制台中看到XHR请求，并可以单击它们转到资源面板，在那里您将能够看到XHR的内容。|991256|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]]]

If you are on a dev channel of Google Chrome:

<a href="http://www.chromium.org/getting-involved/dev-channel" rel="noreferrer">http://www.chromium.org/getting-involved/dev-channel</a>

...you should be able to right-click in the Developer Tools console, and click "Enable XMLHttpRequest logging".

Once it is enabled, you will see the XHR requests in the console, and will be able to click on them to take you to the resources panel, where you'll be able to see the content of an XHR.

blocks|key|991419|text|您可能看到的只是CORS请求的OPTIONS请求被Google+Chrome检查器视为XHR请求。因此，如果你按XHR请求进行过滤，你可能只会看到初始的OPTIONS印前检查请求，它的响应没有内容，并且会感到困惑，因为它看起来像是Chrome拒绝显示响应。禁用过滤器并转到同一URL的下一个请求，这很可能是对应于该CORS印前检查请求的“真实”请求。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|991420|entityMap^0|F|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

What you might be seeing is only the <code>OPTIONS</code> request of a CORS request being treated as an XHR request by Google Chrome inspector. So if you filter by XHR requests, you might only see the initial OPTIONS preflight request, whose response has no content, and get confused because it seems like Chrome is refusing to show the response. Disable the filter and go to the next request for that same URL, which will most likely be the "real" request corresponding to that CORS preflight request.

blocks|key|1205769|text|我遇到了同样的问题:来自flash的POST请求%2B+JSON响应%2B在Chrome检查器中没有显示响应。不过，FF+%2B+FireBug没有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1205770|在响应头部的Content-Type中添加charset=utf-8就解决了这个问题：|1205771|Content-Type:+application/json；charset=utf-8|1205772|我不确定这是否是这个问题的合适解决方案，但至少我现在可以在Chrome+Inspector中看到JSON响应。|1205773|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I encountered the same problem: POST request from flash + JSON response + no response displayed in Chrome inspector. No problem with FF + FireBug though.

Adding charset=utf-8 to Content-Type in the response headers solved the problem for me:

Content-Type: application/json; charset=utf-8

I'm not sure if this is the proper solution for this issue, but at least I'm able to see now the JSON response in Chrome Inspector.

blocks|key|1205584|text|打开资源跟踪，然后检查资源选项卡。如果您选中“始终使用资源跟踪”，则资源跟踪的效果似乎要好得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1205585|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|$]]

Turn on resource tracking, then check the resources tab. Resource tracking seems to work a lot better if you check "always use resource tracking."

blocks|key|991371|text|我得到了空响应，因为脚本正在发送空数据|type|unstyled|depth|inlineStyleRanges|entityRanges|data|991372|die();|code-block|syntax|javascript|991373|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had empty response because the script was sending empty data by 

<pre><code>die();
</code></pre>

blocks|key|1205717|text|在失败回调中，第一个参数有一个名为responseText的属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1205718|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 the fail callback, the first parameter has a property called responseText.

blocks|key|1205891|text|原因可能不仅仅是chrome，而且预览甚至可以被JS代码停止。例如，有一些用于Vue.js的插件叫做vue-resorcese，它有这个问题：Chrome,+no+response+data+after+OPTIONS+request?我和这个问题一起生活了几个月，直到今天发现了这个问题。当前的问题没有给出答案，所以我现在在这里分享它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1205892|详细信息:这个插件有创建XHR对象的下一段代码：|1205893|if+('responseType'+in+xhr+&&+SUPPORTS_BLOB)+{
+++++++xhr.responseType+=+'blob';
}|code-block|syntax|javascript|1205894|这段代码没问题，预览工作正常，直到一些chrome更新。今天，当我评论这篇文章的时候，预览又出现了！所以首先，试着检查一下你的XHR包装器，它可能有类似这样的东西。|1205895|这是一个罕见的问题，因为它只在飞行前使用CORS重现。顺便说一句，右键单击OPTIONS+XHR和REPLAY也会显示预览。|1205896|这就是它了|1205897|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/42172505/chrome-no-response-data-after-options-request^0|13|6|1E|D|1Z|1B|0|0|0|0|0|11|B|1D|6|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|6|7|18|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1A|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1G|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

The reason can be not only in chrome, but also preview can be stopped even by JS code. For example, there is some plugin for <code>Vue.js</code> called <code>vue-resorcese</code>, and it had this issue:
<a href="https://stackoverflow.com/questions/42172505/chrome-no-response-data-after-options-request">Chrome, no response data after OPTIONS request?</a>
I lived with this issue several months until found that question today. Current question never gave an answer, so I now share it here.

Details:
this plugin had next code that creates XHR object:

<pre><code>if ('responseType' in xhr &amp;&amp; SUPPORTS_BLOB) {
 xhr.responseType = 'blob';
}
</code></pre>

This code was ok and preview worked but until some chrome update. 
Today when I commented this away, preview appeared again! So first, try check your XHR wrapper, may be it has something like this.

It was the rare issue because it was reproduced only with CORS preflight. BTW right clicking on the <code>OPTIONS XHR</code> and <code>REPLAY</code> also showed preview.

there you have it

Traditionally I use FireBug to debug my AJAX requests. It lets you examine both the contents of your request as well as the response that was sent back from the server. (it also notifies you in the console when these occur, which is a useful feature that Chrome seems to lack).

In Chrome, I only seem to be able to view the requests, not the responses. When I try to examine the response the UI just displays "No Content Available" (Developer Tools > Resources > myRequest.php > Content). Do I have to turn something on to make the Chrome developer tools remember these requests?

EDIT: In case it matters, these requests are being made inside a Flash object.

View AJAX response content in Chrome developer tools?

服务器

JSON

传统上，我使用FireBug调试我的AJAX请求。它允许您检查请求的内容以及从服务器发回的响应。(当这些情况发生时，它也会在控制台中通知你，这是Chrome似乎缺乏的一个有用的功能)。在Chrome中，我似乎只能查看请求，而不能查看响应。当我尝试检查响应时，UI只显示"No Content Available“(开发人员工具>资源> myRequest.php >内容)。我必须打开一些东西才能让C

问在Chrome开发者工具中查看AJAX响应内容？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Chrome开发者工具中查看AJAX响应内容？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Chrome开发者工具中查看AJAX响应内容？
EN