225

In Firefox, I use Firebug which allows me to view every http request my ajax calls are making. I've switched over my development to Chrome and am liking it so far. My only complaint, however, is that the developer tools don't seem to allow you to view each ajax request. I've had it happen once where the Resources panel showed multiple requests to the same resource, but it's only done it once and never again.

Is there a way to reliably see every http request that a page is making through javascript from within Chrome?

[Edit:11/30/09 11:55]

Currently, to get around this, I'm running Fiddler next to Chrome to view my requests, but if there's a way to do it from within the browser, I'd prefer that.

Improve this question
1
  • 2
    I have the same problem -have tried all the solutions here. Nothing appears in the Response part of the XHR window in the dev tools. It just shows "This request has no response data available". If i run the same code using firebug, it shows up fine. in the cog dev tools settings, I have tried ticking "Log XMLHttpRequest" but this didnt help (response type is application/json). I have to do all debugging in firebug. Firebug also formats the JSON nicely, chrome dev tools doesnt if you can get it to display the response (e.g. by not using ajax).
    – John Little
    Commented Jun 12, 2013 at 12:09

9 Answers 9

Reset to default
383

I know this is an old thread but I thought I would chime in.

Chrome currently has a solution built in.

  1. Use CTRL+SHIFT+I (or navigate to Current Page Control > Developer > Developer Tools. In the newer versions of Chrome, click the Wrench icon > Tools > Developer Tools.) to enable the Developer Tools.
  2. From within the developer tools click on the Network button. If it isn't already, enable it for the session or always.
  3. Click the "XHR" sub-button.
  4. Initiate an AJAX call.
  5. You will see items begin to show up in the left column under "Resources".
  6. Click the resource and there are 2 tabs showing the headers and return content.
Improve this answer
14
  • 2
    Thanks Phil! I had put this aside and been relying mostly on Fiddler. But that XHR button is what I was looking for :D
    – Wes P
    Commented Jun 11, 2010 at 19:10
  • just yesterday i was talking that if chrome tools could do this it would be perfect, thank you.
    – Germán Rodríguez
    Commented Sep 6, 2011 at 14:38
  • 3
    Hi all, tryin to find the "XHR sub-button" I think I may be missing it, can someone tell me where that is? this is what my inspector looks like imgur.com/9e6yDcB
    – David Williams
    Commented Jan 27, 2014 at 17:33
  • 2
    This seems to only happen if an AJAX call gets a response, but it doesn't show you an outgoing request that might not expect a response. Anybody know how to enable that?
    – MoMo
    Commented Jul 28, 2014 at 19:19
  • 1
    If the page redirects on the same window you can use the 'Preserve Log' checkbox at the top of the network tab options (if not you can change that link to open in the same window by setting target='_self' ). Then, for example, you can see the response from the form that got submitted after it redirects you. Make sure to also notice the filter as the responses pile up on new page loads.
    – JeremyS
    Commented Jan 17, 2017 at 19:25
58

The most up-to-date answer to this is: they are listed under the 'Network' button in the developer tools, no longer under 'Resources' like it used to be.

Improve this answer
1
  • 5
    That is indeed where it is now, took me searching stack overflow to find it after upgrading.
    – Kzqai
    Commented Apr 1, 2011 at 20:00
45

Update

Chrome changed how to inspect requests and suggests now to use the Catapult Netlog Viewer with the logs exported from chrome://net-export/

chrome://net-export/

More Info

Old Chrome Versions

You also may use this link in Chrome for more detailed information than the inspector did it.

chrome://net-internals/#events

This shows the log of all requests of the browser while open

Improve this answer
1
  • Could you export that?
    – Pacerier
    Commented Oct 11, 2017 at 20:43
15

don't know as of which chrome version this is available, but i found a setting 'Console - Log XMLHttpRequests' (clicking on the icon in the bottom right corner of developer tools in chrome on mac)

Improve this answer
1
  • 3
    This is the easiest and best way to monitor XHR requests.
    – CourtDemone
    Commented Apr 16, 2014 at 0:03
6

Open up your DevTools and press F1 to access the settings. Look for the console section and check the checkbox for "Log XMLHttpRequests".

Now all of your ajax and other similar requests will be logged in the console.

I prefer this method because it usually allows me to see everything that I'm looking for in the console without having to go to the network tab.

Improve this answer
4

You could use Fiddler which is a good free tool.

Improve this answer
1
  • 1
    Yea, I have Fiddler which is what I'm using to do this. Just looking for a way to do it from within the browser, as it's a bit more convenient.
    – Wes P
    Commented Nov 30, 2009 at 16:55
3

Thanks all person who try to help in this post

I have ubuntu 13.10 and my chrome version is 34.0

For my situation this works

1.open developer tools in chrome(or use right click on your page and then select inspect element)
2.go to "Network" tab
3.find your ajax request in "Name Path" column 
4.click on the specific ajax link

now you should see a new Panel in front of you request 

in this panel select "Response" tab
Improve this answer
1

In the step 5 of Phil, "Resources" is no longer available in the new version of the Chrome. You need to click the page icon just beside the Ajax page listed in the bottom pane with the columns of Name, Method, Status, ...

Then it will show you more panels where you will find the error messages.

Improve this answer
0

You can also just right click on the page in the browser and select "Inspect Element" to bring up the developer tools.

https://developer.chrome.com/devtools

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.