On Tue, 23 Sep 2003, Steve Gibson wrote: > > A feature sometimes offered by HTTP servers is "post dating" the expiration > of content with the "Expires" header. The benefit of this for highly > static content, such as Mathopd is so proficient in delivering, is that > users' web browsers will then not even bother connecting and issuing > "If-Modified-Since" requests which require the server to almost always > return a "304 Not Modified" response. > > If an option could be added to specify the number of minutes or hours in > the future for content expiration, perhaps with wildcards so that certain > directories or certain content types could be given differing expirations, > it could make Mathopd perform even faster in many situations.
I have made a new beta with a "ExtraHeaders" keyword so that you can insert your own "Expires:" header. (The extra headers must be static, so it is probably more useful to send a Cache-Control rather than an Expires header.) If anyone could try out whether sending expires (or cache-control) headers actually reduces network traffic, please let me know. I do not have the means to test this out at the moment. Cheers Michiel
