HttpWatch Help Version 11.x
Using HttpWatch / User Interface / Request View / Overview
In This Topic
    Overview
    In This Topic

    The actions listed on this tab provide a breakdown of the operations required to process the selected requested:

    Display URL

    This action indicates that the browser started processing a URL request and will complete the request in one of three ways:

    Resync URL

    The browser started a refresh operation because the user pressed F5 or clicked on the Refresh toolbar icon. This will be processed in one of two ways:

    Get Latest

    The browser is performing a forced update operation, typically due to the user pressing Ctrl + F5. This is always processed as an unconditional GET or POST request.

    Submit Form

    This is usually the result of an HTML form being submitted and causes an HTTP POST to be sent to the web server.

    History Cache

    The browser requested a copy of the page or resource from the list of pages held in the history list. This can occur when a page is revisited using the Back button.

    Started At

    This action shows the date and time at which the browser started to process the HTTP transaction. The request may not be immediately sent out on the network due to the following factors:

    DNS Lookup

    The browser is resolving a hostname, such as www.microsoft.com, into an IP address, e.g. 207.46.244.188, prior to attempting a connection to the web server .

    Connecting

    Indicates that no existing connection to the server was available for use by this request and the browser is creating a new TCP connection to the specified IP address.

    Connected

    A new connection has been made to the server using the specified local IP address and port number (<ip>:<port>).

    Connection Reuse

    An existing connection to the server was used by this request instead of a new connection.

    HTTP Request

    This shows that an HTTP request that was sent over the network to the server.

    HTTP Response

    This shows that an HTTP response was received from the web server.

    Read Cache

    This action can occur in three situations:

    1. The browser sent an If-Modified-Since header and received a 304 Not Modified response. The content would then be read from the cache because the 304 response indicates that it is still valid. The Content-Length header in the response will always be zero or absent because the HTTP 1.1 spec defines the 304 status code as never returning content.
    2. The browser decided not to send a HTTP GET request because there is an entry in the browser cache that either has a valid expiration date or has been recently checked. The Result column will show (Cache) in these cases.
    3. The browser is in 'Work Offline' mode

    Redirect

    The web server returned a 3xx response (usually 301 or 302) that redirected the browser to a different URL.

    See Also