I guess the reason why it takes so long until you see the response in the new tab is that it is encoded into a data URL <https://developer.mozilla.org/en-US/docs/Web/HTTP/data_URIs>, which might cause problems while decoding.
To see the full response, you have two possibilities: 1. Increase the value of the preference extensions.firebug.netDisplayedResponseLimit <https://getfirebug.com/wiki/index.php/Firebug_Preferences#netDisplayedResponseLimit> via about:config <http://kb.mozillazine.org/About:config>. 2. Right-click the request, choose *Copy Response Body* from the context menu and paste it into your favorite text editor. Best regards, Sebastian On Thursday, February 18, 2016 at 10:17:52 AM UTC+1, [email protected] wrote: > > Hi > > I'm dealing with parsed responses from our server and opening save-data > files well above 1.2MBs in size (plain text) > > The messages are naturally too large to display within firebug so the > option is available to display the Response in the browser. > However the result takes ages to load and then cuts off at the end rather > than show the full response. > > Is there any way to retrieve the raw data so I can load it on my own > text-editors in full? > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/13a7c86b-d14d-42c4-a299-4831bf2035e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
