<-- back to the mailing list

Caching and status codes

Sudipto Mallick smallick.dev at gmail.com

Fri Nov 6 07:27:11 GMT 2020

- - - - - - - - - - - - - - - - - - - 

Instead of "permanent" caching (what is permanent?) I am thinkingabout using timestamps.

So, for a requested resource, (if it is available) return a timestampwhich denotes when the resource was last changed.

When requesting the resource again, send that timestamp with it andthe server checks if the cache is stale or not and respondsaccordingly (either "resource is modified after $(old_timestamp) sohere is the new resource and it was modified on $(new_timestamp)" or"the resource was not changed after $(timestamp)").

But the problem is, where does the timestamp goes in the request and response?

~smlckz