To work with an HTTP or HTTPS message, select it in the Recording Editor in either Icon or List view.
The recorded messages appear as a series of icons or rows (depending on the view).
For recordings with more messages than are shown in the display, scroll left or right to dynamically load the next messages. Newly loaded messages appear transparent until they are fully loaded. Dynamic scrolling displays recorded content in completed recordings in a continuous line as you scroll from left to right and back again. This works in both Icon and List views within the Recording Editor.
Once a message is selected, its details are presented in the sections below. Each message contains both request and response information. The detailed information available for a message may be summarized as follows:
- General request and response information. The request URL, for example.
- Request and response headers
- Request and response content
The Summary section displays the following information
The number of the message within the recorded sequence
The IP address from which the request was sent
The IP address of the responding host
The HTTP method. In this case, the method was POST. Other typical HTTP methods are GET, POST, PUT, HEAD, and DELETE
Always http for recordings.
The response code is the code returned by the responding host for this request. In this case, the response code was 200, which signifies that the response was returned without an error. A Non-200 response code may indicate an error condition
The URL indicates the requested resource on the host system.
If the message is in a binary format, check Decode this binary encoded message using one of the drop-down options
In the remaining Detail views (below Summary), Request information for the selection is presented in the left column, while Response information is presented on the right.
Request and Response Headers
HTTP request and response headers contain various parameters that control the interaction between the requesting client and the responding host. For example, the request will typically contain the header Accept–Encoding. In this case, the value for that header is list-contains=gzip which tells the responding host the form of the response the requesting client is prepared to accept. The response will typically include the header Content-Type or Content-Encoding.
- Response Headers
Response header detail information is shown for the message selected above.
- Request Headers
Request header detail information is shown for the message selection.
HTTP Head Request support
As of SOASTA 50, support for HTTP standard HEAD messages takes its place alongside previously supported message types GET, PUT, POST, an DELETE.
Just as with any other message type, generic HEAD messages can be added to a message test clip via the Messages/Actions tab, Operations list (shown above). Double-click a HEAD message to display and edit its properties in the Clip Editor lower panel.