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

Display URL

The browser started processing a URL request. Depending on browser state, request cache mode, cache directives and service workers, the result may be served from a memory, disk or prefetch cache; handled by a service worker; revalidated with the server; or fetched from the network.

Resync URL

The browser started a refresh operation, typically because the user pressed F5 or selected Refresh. The browser may reuse fresh data, revalidate cached data with validators such as ETag/If-None-Match or Last-Modified/If-Modified-Since, ask a service worker to handle the request, or fetch data from the network. The exact sequence depends on browser and page state.

Get Latest

The browser started a hard-refresh or other request intended to obtain updated data, typically after Ctrl+F5. This normally bypasses or revalidates browser caches, but HttpWatch does not guarantee one unconditional request sequence; service workers, request cache modes and browser policy can affect processing.

Submit Form

This is usually the result of an HTML form submission. The request method and body depend on the form and script that initiated it; common methods include GET and POST.

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:

• The request will be blocked if there are too many outstanding requests to the same server or proxy. It is often this delay that is the most significant factor for the time taken to retrieve an image.
  
• The host name may need to be resolved into an IP address see DNS Lookup below.
  
• A new connection may be required if an existing connection cannot be reused.

DNS Lookup

The browser is resolving a host name, 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 or proxy was available for this request and the browser is establishing a new transport connection. This normally uses TCP for HTTP/1.x and HTTP/2, or QUIC for HTTP/3.

Connected

A new transport connection has been made to the server or proxy 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 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 indicates that stored response data was read from a browser cache. Common cases include:

1. The browser revalidated a cached object by sending an If-Modified-Since header and received 304 Not Modified. The 304 has no response content, so the stored representation supplies the content. A Content-Length header on a 304 does not describe response content.
   
2. The browser reused a cached representation without making a network request for this entry. The Result column shows (Cache).
   
3. A service worker may use cached data while handling a request. HttpWatch identifies service-worker handling separately from a direct browser-cache result.

Redirect

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