Specifying HTTP Headers

A P P E N D I X E

Note - The information in this appendix is for advanced users who want to tune test bundle downloading to devices. To use these instructions successfully, you must understand HTTP headers. An error in the configuration files described here can have serious negative consequences.

For a tester, two files can influence the contents of the HTTP response headers generated by the Relay when a test device requests a bundle:

CentralInstallDir/admin/shared/conf/httpheaders.properties: An administrator can modify this file to change the default HTTP headers for all harnesses.

TesterHarnessInstallDir/conf/httpheaders.properties: A tester can create this optional file to specify HTTP headers for a particular harness. This file, if present, overrides CentralInstallDir/admin/conf/httpheaders.properties.

The default CentralInstallDir/admin/shared/conf/httpheaders.properties file contains these lines:

Cache-Control=no-cache
Pragma=no-cache

These lines disable caching in many networks and devices. The second line is for HTTP 1.0 devices. Disabling caching is important for downloading test bundles by a URL bookmark. For tester convenience, the Relay gives every bundle the same URL, namely
http://ipAddressPort/appContext/jad/harnessID/getNextApp.jad.
When a tester requests this URL with a bookmark, a caching facility in the network or the test device can repeatedly return a test bundle that has already been run. Disabling caching forces the device or network to obtain the correct bundle from the Relay.

You can create or modify a harness-local httpheaders.properties file to disable caching by your network or by a particular test device. You can also add lines to perform additional network or device tuning.