top of page

A Fresh HTTP Response Can Contain Old Sensor Data: Test Both Ages

Nov 5
3 min read

A dashboard can receive a successful HTTP response while displaying a measurement captured long before the request. Check response reuse and measurement freshness separately. An HTTP cache policy describes handling of a response; it does not prove that the sensor has sampled again.


Original conceptual illustration of a fresh http response can contain old sensor data; not a specific product or live software screen

Original conceptual illustration; not a specific product, live software screen or customer installation.


Key takeaways


  • Response age is not measurement age.

  • Validation can confirm unchanged old data.

  • Test source stoppage as well as normal refresh.


1. Draw the complete read path


List the source sensor, gateway, ingestion process, stored reading, API, intermediary cache and browser. Mark where the acquisition timestamp originates and where quality is assigned. Without that map, repeated screen refreshes can become an expensive way to redisplay the same underlying record.


Use a sanitised test point to investigate the path. Record the measurement timestamp and identity as well as the request time. A clock discrepancy can create apparent age even when transport is fast, so document time zones and clock assumptions alongside the data.


2. Separate HTTP freshness from sample freshness


RFC 9111 defines response caching and validation. A stored response can be reused according to its freshness rules. The Age header estimates response age since generation or successful validation; it is not the age of the physical measurement described in the body.


A response generated now may legitimately report the most recent stored sample from ten minutes ago. Conversely, a cached response can hide a newer sample already present at the origin. These are different failure questions and need different test evidence. Do not make one green connection icon stand for both.


3. Apply the correct cache vocabulary


An unqualified no-cache response directive requires successful validation before reuse; it does not simply mean that storage is forbidden. A no-store response directive prohibits storing and reusing the response as defined by the caching rules. Use the documented policy suitable for the data and access requirements.


A conditional response confirming an unchanged representation can be normal. It does not establish a new sensor acquisition. Inspect the application timestamp and quality state after validation. Avoid promising that a browser hard refresh or adding arbitrary URL parameters solves an upstream stale-data problem.


Original explanatory workflow for a fresh http response can contain old sensor data: test both ages

Original explanatory diagram. Hypothetical values and proposed checks are described in the text; this is not a product specification or field result.


4. A hypothetical freshness acceptance test


Suppose a test API responds at 12:00 with a sample timestamp of 11:50 and an HTTP Age of zero. The response can be newly generated while the measurement is ten minutes old. If the application freshness limit is two minutes, the point should be treated according to that overdue-data requirement.


Next, introduce a new synthetic sample at the origin and inspect whether the normal client receives it within the agreed bound. Preserve headers, timestamps and the displayed value. Then stop the synthetic source and check that successful API reads do not keep resetting the measurement freshness indicator.


  1. Identify acquisition time and response time independently.

  2. Record cache headers during normal reads.

  3. Inject a fresh synthetic sample at the origin.

  4. Stop updates and verify the overdue-data response.


5. Specify the reader-facing result


For monitoring design, show what time a value represents and how overdue or uncertain data is communicated. Define the threshold with the application owner, including normal reporting intervals and permitted delays. A blanket limit copied from another site can make either nuisance warnings or hidden gaps.


This is an integration test pattern, not a statement that a particular cache control, freshness widget or API option is available in every ProSight Software deployment. Bring the source timing, interface documentation and acceptance requirement to ProSight Software so the supported implementation can be confirmed.


Related guide and project resources




Technical references



Need help with your application?


Send the relevant point list, equipment documentation and a sanitised example of the behaviour you need to verify. Confirm the available functions and integration requirements for the exact equipment and deployment.










Comments


prosight-software-logo (1).png
bottom of page