Hi, Thanks for your reply.
I haven't found getting Apache to do it (mod_expires) to be very flexible. Mason looks to be ideal. Most pages can default to 1 hour. I can then change any that need something shorter by setting an attribute in the component. It works on IE but Netscape won't do it. I wonder if I should be setting more than one http-equiv header. Do they exist for last-modified etc? All the best. Duncan -----Original Message----- From: John Peacock [mailto:[EMAIL PROTECTED] Sent: 17 January 2007 17:56 To: Duncan Garland Cc: Mason-Users Subject: Re: [Mason] Client side page caching Duncan Garland wrote: > Here's an example of a page which won't cache under Netscape: > > <meta http-equiv="expires" content="Wed, 17 Jan 2007 18:23:31 GMT" ></meta> I have not found that the meta expires header alone will do what you want. Indeed there are strange things that happen if the client and server's clocks are not synchronized. For our dynamically generated websites (not using Mason), we make sure that the following response headers are sent by the webserver (e.g. for 120 minutes expiration): Date: Wed, 17 Jan 2007 17:51:40 GMT Last-Modified: Wed, 17 Jan 2007 17:51:40 GMT Expires: Wed, 17 Jan 2007 19:51:40 GMT HTH John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
