This repository was archived by the owner on Nov 22, 2018. It is now read-only.
This repository was archived by the owner on Nov 22, 2018. It is now read-only.
Update how certain cache directives are handled #83
Closed
Description
no-store
on request:
This should by-passShimResponseStream
since we can't store any part of the response so there's no point in capturing the responseno-cache
on request:
We can "validate" by asking the server to regenerate the response. As such we shouldn't skip the capturing of the response and update the cache entry if possible.max-stale
The case where no limit is specified, which means any stale response can be served, is not handled.proxy-revalidate
Same effect asmust-revalidate
Also the header
If-Unmodified-Since
is being used incorrectly. The correct header to check for in when determining if content is modified isIf-Modified-Since