Which inspector tabs appear#

The right pane of a Web Debugger tab is the inspector. It is empty until you select a request. It then shows that request and response across a row of tabs at the top.

The set of tabs depends on the content of the request. A row that has no body has no Request tab.

Tabs that are always present#

These tabs are always present.

• Overview: a full breakdown of session info, timing, sizes, request and response details, TLS, query parameters, and cookies.
• Headers: request and response headers in the order they were sent.
• Composer: replay this request with edits.

Tabs that depend on the content#

These tabs only appear when the selected request has the right content.

• Request: only when the request has a body.
• Response: only when the response has a body.
• Form Data: only when the request body is form-encoded.
• Auth: only when GraphDagger detects an auth payload (JWT, OAuth token, SAML assertion, basic auth, and so on).

Find text across the tabs#

A search field above the tab row searches across the inspector. When a search is active, each tab shows a small count badge next to its name with the number of matches in that tab. Select a tab to open it and to highlight the matches inside.

Select more than one row#

Select several rows in the entries list, for example with shift-click. The inspector then changes to a comparison mode, and the Overview tab shows aggregate statistics for the whole selection. The tab row works the same way. Each tab shows only the content that makes sense for a comparison.