Peter Small ([EMAIL PROTECTED]; Tuesday, June 24, 2003 8:16 AM): > I've got a system of agents that exist on the Web as javascript > documents. I need to be able to monitor how often they are accessed.
> Seems a simple enough task for a log analyzer, but the problem I have > is with server caches. If they cache my agents (js documents), I have > no accurate way of knowing how often they are accessed. > Has anybody found a solution to this problem (i.e., preventing js > documents being cached)? Depending on your server configuration and access points there are several approaches. The first is to use HTTP headers to expire the document and declare it as non-cacheable. See sections 14.9, 14.21 and 14.32 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html. You may be able to set this up at the server level for those pages or in the pages that serve them using server-side scripts. If the logic of your site permits it you can require a POST request to access the agents -- browsers don't cache post requests. You might also be able to include a random or changing parameter in the URL that makes each link to the page appear to be new to the browser. This won't stop cached copies from bookmarks, but will from those links on your site. -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
