Forrest Aldrich wrote:
The only thing that would vary, in this case, is if the image had been updated/changed, in which case it would need to be pulled in from the backend DB. The images are 768k jpg (or less), and because it's a cache, it's disposable...
That is not a vary ;-) And it's up to your content handler (or manually by overriding the cache expiration directives) to report a legitimate amount of time the content will remain fresh (or, 'fresh enough'). Vary is when your server is prepared to serve an .en or .es file, for example, depending on the browser's (user's) preference between english or spanish, or if your content changes when the user comes in with a netscape browser v.s. an IE browser. Bill --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|