views:

100

answers:

3

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.

A: 

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

no
Resource tracking is definitely on. I can see the requests being made, and the headers of those requests, just not the content. (NOTE: this only applies to AJAX requests, and may only apply to ones made in Flash).
Ender
That's weird. I don't use flash, maybe that's the problem... might be worth it to try a more recent dev build of chrome/chromium if you haven't yet.
no
+1  A: 

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.

loislo
+1  A: 

If you are on a dev channel of Google Chrome:

http://www.chromium.org/getting-involved/dev-channel

...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.

Masterov