Local implementation lab · 03

Which request reached the origin?

Implement one response function, predict the next body and request count, then compare actual browser reuse with the origin log.

One resource, two policies

Response policy

Changing the origin does not invalidate a fresh browser entry. Keep DevTools “disable cache” off; use these buttons rather than reloading.

Ready. The starter deliberately leaves responseFor unfinished.

Successful browser fetches: 0
Summary requests at origin: 0
Current origin version: 1

Body the browser received

No response yet

Origin request log

[]

A browser fetch can expose status 200 after the network returned 304 and reused a stored body. The origin log records network status; these are different observations.