Verify HTTP responses at every VoxCAST POP for a given URL. Returns the HTTP response code and other interesting information from each POP.


device_id (required)
Numeric Voxel device id, available from voxel.devices.list
path (required)
A path to a content object, e.g., "/path/to/content"

Example Response

  <facility name="AMS2" up="yes">
    <performance from="LGA2">
      <header>HTTP/1.1 200 OK</header>
      <header>Date: Mon, 06 Jul 2009 05:52:25 GMT</header>
      <header>Server: Apache</header>


VoxCAST users who wish to do their own internal monitoring of VoxCAST nodes, for whatever reason, should use this method instead of trying to implement their own HTTP tests. This method makes use of internal VoxCAST state information to dynamically decide which POPs (facilities) to test. Only POPs that are currently enabled in VoxCAST will be returned in the results. Occasionally VoxCAST POPs are brought down for maintenance or upgrades. While a POP is down, it serves no traffic, and testing requests sent to that POP may fail, so we exclude downed POPs in this call. Performance values are the times in seconds from the start of the request until name resolving was completed (namelookup_time); connection to the VoxCAST server was completed (connect_time); all pre-transfer request information has been sent to VoxCAST (pretransfer_time); and VoxCAST responds with the first byte (starttransfer_time). All response headers from VoxCAST are included in the output.

Method Specific Error Codes

100: Unknown device
The device_id passed in can't be matched to a valid device.
205: SNMP polling failure (explanation)
An error occurred while polling an internal SNMP OID. An explanation may be specified in parenthesis.