Compare two recorded responses after a cache configuration change
Admin ·
Two responses for the same resource may carry different caching instructions after a deployment. Capture a comparable request on each side of the change.
Read a cache instruction change
If the first final response has Cache-Control: max-age=60 and the second has Cache-Control: max-age=600, the table shows Changed and displays both values. If Age disappears, the table labels it Removed.
Check duplicates and filtered values
A different order of values for the same repeated field counts as a change. A different capitalization of a field name does not. For Set-Cookie, changed values are detected before the display filter withholds them.
Decide whether a difference is expected
Compare two captures of the same resource and status. A changing Date field can be expected on different requests. A change from private to public in Cache-Control is a different kind of finding and needs review against the content being served.
Record request method, response status and capture time with the comparison. A cached response compared with a redirect can produce a long diff that says little about a recent configuration change.
Common questions
Does the diff compare every redirect?
It compares the last block of each input. Copy a particular pair of earlier status blocks to compare those hops instead.
Does it prove two responses are equivalent?
It compares the recorded status and fields with the documented normalization. Bodies, timing and later requests are outside the report.
Sources
Put it into practice.
Related guides
- Read a saved HTTP response header dump
- Interpret a security header grade
- Read recorded redirect hops
- Compare DNS captures after a record change
- Compare saved registry responses
- Compare Private and Shared Cache Freshness
- Compare Requests Against a Vary Header
- Compare Saved Redirect Chains
- Set Browser and CDN Freshness
- Check Version Details in Saved Server Headers