Web Services tab
Web applications today rely heavily on calling other web services. With many web service calls happening, it can be challenging to understand the results of a specific call during a specific request. The Services tab gives a unified view of all of a selected request’s web service activity; calls from your Node.js application and calls from your browser’s Fetch and XmlHttpRequest APIs are brought together in a single tab. The image below shows two HTTP calls made from the browser.
There are four main components in the services tab:
The filter bar, shown below, allows users to include or exclude HTTP calls events based on whether they occurred in the server or the browser (E), or based on the response code of the HTTP request(F). Filters can be reset to their default(G).
Web Services table
The Services table shows a list of all HTTP client calls made as part of the currently selected request. The URL, HTTP method and status code are shown, as well as the duration of the service call and when that service call occurred in the currently selected request. Additionally, the icon on the far left indicates whether the service call was made from the browser (a diamond), or the server (a circle). If the request was made to a glimpse-enabled endpoint a blue arrow will appear next to the URL. Clicking this arrow will navigate to this request in Glimpse, i.e., it will go from the view of the service call from the client’s perspective to the server’s perspective. This is illustrated below.
Request & response details
Details about the selected web service call are shown in the request/response details section. This is a similar view to what is shown in the request details. You can view headers, body and the query string for the request. At this time, cookies are not shown for web service calls made from the browser, as the browser security sandbox make cookies unavailable to Glimpse inspection. If the body is JSON, XML or HTML content, the body tab will format the content according to its type, and for JSON, expand/collapse affordances will be provided to easily navigate JSON payloads.