Closed
Bug 1250494
Opened 9 years ago
Closed 9 years ago
Network Monitor - cannot read invalid json response
Categories
(DevTools :: Netmonitor, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 859138
People
(Reporter: amanteaux+firefoxbz, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160210153822
Steps to reproduce:
I try to debug the response sent by a server:
- with a Json content-type header,
- with a non json content (e.g. plain string).
I am using:
- the default developer tools provided with Firefox (F12),
- the network tab,
- I click on a json request,
- I go to the Response tab of the json request.
Actual results:
The red error "SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data" is displayed at the top of the json request tab.
I have not found any way to see the actual HTTP request body response from the server.
Expected results:
If the developer tools cannot parse the HTTP request body, it should display the request body as text.
This problem appears with the Json parser, but I guess it is also present with the image parser: https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor
Moreover, it would be awesome if the user could change the parser used by Firefox in this tab: Text, JSON, Image, XML... For example, if the server sends a wrong content type but returns a json object, we would be able to select the json parser to render a human readable object.
A dropdown box could be displayed above the error message :)
Summary: Developper Tools - Nework - cannot read invalid json response → Network Monitor - cannot read invalid json response
I believe this is the same as bug 859138, so I'll dupe it there. Feel free to reopen if it seems different.
As a workaround, you can right-click a request and "Copy Response", but then you'd have to paste it somewhere.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•