Take the 2-minute tour ×

I am using Google Chrome Developer Tools to try to see the response of some AJAX url's.

The problem is that when I click on the NETWORK TAB, then on the link, then on RESPONSE, I see this text : "THIS REQUEST HAS NO RESPONSE DATA AVAILABLE".

I have been using FIREBUG and I am 100% sure there is a response from that page.

Can somebody help with this ?

Thank you !

share|improve this question
i have the same issue. have tried everything and am tearing out hair... –  John Little Jun 12 '13 at 12:14
@JohnLittle Don't tear our your hair :-) See if the response below (although a little bit late) solves your problem. –  Miljen Mikic Sep 12 '13 at 10:02
add comment

1 Answer

Had the same issue, and Wireshark saved the day. You are right, server did respond, but it responded without the response body and that's why Chrome showed that there is "no response data available". Here is the captured response:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Length: 82
Date: Thu, 12 Sep 2013 07:14:50 GMT

As you can see from the capture, there is no response body, just the plain HTTP header. In my case this is a bug on the server side because I have sent something that confused the server. It is a bug because server should have responded, at least with some error message.

In any case, I would recommend to capture the traffic and examine the response there. In some versions of Chrome there were the cases (Chromium bugs) when Chrome showed "no response data available" and Firebug showed the response. With Wireshark or similar traffic capture tool you are 100% sure.

share|improve this answer
Firebug correctly shows the response body, but Chrome does not. It sounds like your issue (and hence the fix) is not the same as @nevergone. –  Dustin Sparks Nov 22 '13 at 14:50
@DustinSparks You are wrong. First of all, both of us had the same situation - Chrome showed "request has no data available" (Firefox is more or less irrelevant). Second, the solution I am suggesting is universally applicable - using Wireshark indeed is a best way to record traffic between client and server, browser-independent (and thus, browser-bug-independent). –  Miljen Mikic Nov 22 '13 at 15:33
You both had the same result, but not the same problem - his was actually providing data in the body (as proven by firebug), yours was empty. Using a 3rd party tool is irrelevant in this situation; especially considering he was already able to see the response data in firebug. Why would he need Wireshark to see what he can already see working with another tool he's already using? The question wasn't about Firefox or Wireshark, it was how to do it in Chrome. Either way, there is a documented Chrome bug that shows this happening. Apparently it hasn't been fixed yet. goo.gl/gNk0L9 –  Dustin Sparks Nov 22 '13 at 19:25
@DustinSparks And it is not the only Chrome bug regarding that specific message, follow the link that I submitted in my answer. Basically, what you are saying is the same as in my last paragraph ("In some versions of Chrome there were the cases.."). The only difference is that I will always recommend using Wireshark because it is the best tool for such purpose and it has been helpful to me in many occassions, much more than Firebug or Developer tools. They are suitable as "first aid kit", but for serious traffic analysis there is no alternative to Wireshark. –  Miljen Mikic Nov 23 '13 at 11:56
add comment

Your Answer


