[Webkit-unassigned] [Bug 22920] Inspector Request Headers Should Show Data/Variables/Parameters Sent With Request

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=22920





--- Comment #12 from Patrick Mueller <pmuellr at yahoo.com>  2009-08-19 11:55:26 PDT ---
Created an attachment (id=35130)
 --> (https://bugs.webkit.org/attachment.cgi?id=35130)
work in progress showing query string and form data

current progress.  I've redacted bits of the UI, as this was from a live
session w/gmail - which turns out to be a great test case for this stuff.

You can see new "Query String Parameters" and "Form Data" elements after the
"Request Headers" but before "Response Headers".  They only appear if
applicable, most of the time they won't be there at all.  Note this was a case
of a POST with a URL that had query string parms in the URL as well as form
data, so both sections appear.

The key/vals are laid out with the exact same styling as the headers and
values; this is somewhat problematic - there are already sizing issues with the
header keys in some cases, but that will have to be fixed later, for all of
these sections.

When collapsed, the number of pairs will be displayed in the collapsed title,
just as with the Request and Response Headers.

The values are displayed raw.  For example, look at the bottom of the image,
with the req3_json key.  URL encoding goodness.  I feel like it's important to
display the raw value, but obviously useful to show the decoded one, so the
decoded version is available as a tooltip, as shown in this example (the yellow
div at the bottom of the image).

The last thing to do is figure out what to do with an HTTP request payload
which is NOT form data.  I'm currently thinking of just doing the simplest
possible thing and displaying it as another (optionally visible) section called
"Request Data" or something.  With one element called data, whose value is the
actual payload.  Ideally, the payload would actually be displayed as a peer of
the response payload - ie, the div underneath all the headers (where, instance,
an image might be displayed if the resource was an image).  Seems like perhaps
this is something that can be properly done in another bug, which could do some
other payload enhancements like render JSON in a friendly way.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.