Firefox developer tools truncates long network response, Chrome does not show

Question

I used (winter 2018) to be able to capture a JSON response using either Chrome or Firefox developer tools. Now for the long ones I need (>> 1 MB) Chrome doesn't work, and Firefox truncates at 1 megabyte. This was using the developer tools. Short ones work on Firefox.

There was a recent response on "firebug" saying it was fixed in Firefox, but no. This was a response from familytreedna.com of a big JSON file used to construct a tree. The web page works ... but it takes a long time to download the data file (11 megabytes!) Is this a bug or "feature" in the developer tools.

Inscribe

Please add a minimal reproducible example, including an illustration of the problem. The cause may be in the way you handle the data or in the way you interact with a server, or in your server logic. – Sold

https://mcmap.net/q/302377/-how-to-debug-ajax-response may help to find out if the response is really truncated in the runtime, or it's just the devtools UI not showing it all. – Sold

Answer 1

Firefox dev tools network inspector still truncates responses to 1MB by default.

You can change or disable the limit by navigating to about:config and changing devtools.netmonitor.responseBodyLimit. To disable the limit, set it to 0.

Norland

Is it possible devtools.netmonitor.responseBodyLimit does not apply to WebSocket frames in the WS Inspector? – Specific

For WS I believe it is devtools.netmonitor.ws.messageDataLimit bugzilla.mozilla.org/show_bug.cgi?id=1565226 – Specific

is there a similar thing in chrome? it seems to also truncate without warning. it just shows nothing when large – Evanne

This works, but it's very slow. I'm not sure why its fast to write a large object to the console, but slow to view it in the network tab. – Fairlie

works perfectly after setting it to 0 thanks a lot! – Sugarplum

devtools.netmonitor.requestBodyLimit just to mention if your request is also huge. But 0 doesn't work for me in DevTools and it is still truncated. Copy as Curl rules. – Doykos

Figured I'd say this because it might save somebody a couple of seconds: when you change the setting to 0, the "Response has been truncated" immediately disappears, but Firefox will still be rendering the truncated response until you refresh the tab. – Reside

Answer 2

Update

See @Joni's answer for more info about it.

Original Answer

This bug already reported on https://bugzilla.mozilla.org and fixed in Firefox 61.

So update your browser to v61 (if you didn't already) and feel free to report the issue on bugzilla if it's still exists.

Urbana

As of Firefox 73, responses are still truncated to 1mb by default. The "fix" was to add a user preference to remove this limit. So Joni's answer is more useful here. – Heilman

This is still happening in 109. (latest version today) – Mastoiditis

Answer 3

Yes, about:config and changing devtools.netmonitor.responseBodyLimit to 0 fixed the issue for me in which I could not copy much text at all, but now can copy well over 1,000 words, though sometimes the browser will crash (not for lack of system memory though).

Quilting