|
|
|
@ -2,7 +2,7 @@ Flight provides built-in support for HTTP level caching. If the caching conditio
|
|
|
|
|
Flight will return an HTTP `304 Not Modified` response. The next time the client requests the same resource,
|
|
|
|
|
they will be prompted to use their locally cached version.
|
|
|
|
|
|
|
|
|
|
## Last-Modified
|
|
|
|
|
### Last-Modified
|
|
|
|
|
|
|
|
|
|
You can use the `lastModified` method and pass in a UNIX timestamp to set the date and time a page was last modified.
|
|
|
|
|
The client will continue to use their cache until the last modified value is changed.
|
|
|
|
@ -12,7 +12,7 @@ The client will continue to use their cache until the last modified value is cha
|
|
|
|
|
echo 'This content will be cached.';
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
## ETag
|
|
|
|
|
### ETag
|
|
|
|
|
|
|
|
|
|
ETag caching is similar to Last-Modified, except you can specify any id you want for the resource:
|
|
|
|
|
|