Bug 39711 – provide parsed view of get params

• Component: Web Inspector (Deprecated)
• Status: RESOLVED DUPLICATE

[mbrevda]

Firebug parses the sent parms, as well as any responce (think: json) so that they can be viewed in a clean key:value table. This is in addition to the raw request url and response, making finding the value your looking for simpler. Would be nice to have this as well!

[mbrevda]

Created attachment 57074 [details]
firebug demo

[mbrevda]

http://code.google.com/p/chromium/issues/detail?id=45070

[Patrick Mueller]

This was previously implemented via Bug 22920; perhaps there's at least some code to reuse there, if it's been removed since.

[Patrick Mueller]

I tried the test case 

    WebKit/WebCore/manual-tests/inspector/display-form-data.html

which is the test case for Bug 22920, on nightly r60266.  All tests appear to pass.

Trying that test on Chrome/Mac 6.0.408.1 dev shows multiple problems:

- test-2 does not show any query string parameters when it should
- the tests get an uncaught error during an XHR request, which causes later tests to fail

The tests currently do sync- and async- XHR testing, since I figured the control paths under the covers would be a little different, and I wanted to make sure we covered those cases.  Perhaps we need to put some kind of guard around the sync- versions.  Or perhaps the fact that tests all send requests to http://example.org is part of the problem, which end up generating 404 status codes.

Not quite ready to mark this as WORKSFORME, and just say this is a Chrome problem, and not a WebKit problem.  Doing a little more investigation ...

[Patrick Mueller]

- commenting out the sync- calls gets you a bit further than calling them.

- running the file against a real server gets you a bit further than running against a file:// url.

Still, the best I can do, I don't see all of the data the tests expect.  It appears the query string params are the biggest problem.  I think perhaps we need to refresh the query string params in different/additional places to get Chrome to display them.

I think we need to change this test to run against a real server, and should see if we can run the sync- tests in timer events, to eliminate the general Xhr issues when running in Chrome.

[Pavel Feldman]

Patrick, what you are describing is just a regression, it affects both WebKit and Chromium. I fixed it under: https://bugs.webkit.org/show_bug.cgi?id=39848.

As a result, we show GET query parameters + Post payload + form data. We do not response as JSON as this bug requests, so I am leaving it opened.

[Patrick Mueller]

(In reply to comment #6)

> We do not response as JSON as this bug requests, so I am leaving it opened.

Let's close it as a DUP of Bug 37488 instead, if all that's left is JSON display of the response (and presumably the request)

[Patrick R. Gansterer]

*** This bug has been marked as a duplicate of bug 20628 ***