Browse Prior Art Database

HTTP ping Disclosure Number: IPCOM000014031D
Original Publication Date: 2002-Sep-19
Included in the Prior Art Database: 2003-Jun-19
Document File: 1 page(s) / 39K

Publishing Venue




This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 67% of the total text.

Page 1 of 1

HTTP ping


    Measuring web browser speeds by using HTTP redirection headers. Problem

    To measure web browser effective speed, with respect to HTTP servers, without installing any software on the client side, in order to provide a reasonably accurate measurement of clients on the web, including clients behind firewalls.


    Web client effective bandwidth, with respect to an HTTP server, can be measured by sending an HTTP redirection header to clients, and measuring the time it takes for a client to ask for the new redirected URL. We refer to this technique as "HTTP ping."

    This technique uses a gateway (in front of a web server) that sends an HTTP redirection header to clients. Users always browse the site via the gateway (this is the official published site name). The gateway examines the HTTP request, sends back a redirect header (302) to the client, and begins to measure the time from the moment of the submission of the redirect header. Once the client returns with the request for the redirected URL, the round trip time can be calculated for that specific client.

    A new redirect header is sent to the client with the original URL, which was requested by the client initially.

    The third time that the user accesses the gateway, the request is relayed to the actual HTTP server without any further intervention.

    This entire process of redirection can be activated periodically and selectively, and could conform to any policy. " Accrue Insight" reports offer si...