On Fri, Feb 13, 2009 at 9:40 AM, sebb <seb...@gmail.com> wrote: > The Expires date should not be more than 1 year in the future: > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21 > > [The example on the askapache web-site has a date of "15 Apr 2010" > which is currently more than a year hence.]
I didn't realize that setting the date that far ahead was incorrect. For our purposes here, expiration dates of less than one year in the future will still show the same behavior. > I don't think that this can be changed without writing Java code. > > Feel free to raise an enhancement request for the Cache Manager to > handle Expires headers. If so, it would be helpful to provide details > of a publicly accessible server that can be used to test any changes. I went ahead and wrote this myself. I have implemented this as an extension to the Cache Manager. When a URL is successfully loaded, it stores the Expires header value in the cache. On subsequent requests for the same URL, it short circuits the sample if the URL is present in the cache and the expiration date is later then now. I'd like to contribute this code back to the project. What is the best way to do so? --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
