On 13/02/2009, Chris Copeland wrote:
> On Fri, Feb 13, 2009 at 9:40 AM, sebb 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"
On Fri, Feb 13, 2009 at 9:40 AM, sebb 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 di
On 12/02/2009, Chris Copeland wrote:
> Hello,
>
> I use a far future Expires header for static content in my web
> application (technique described at
> http://www.askapache.com/htaccess/apache-speed-expires.html).
As it says, that site is not supported or endorsed by the ASF.
The Expires dat
Hello,
I use a far future Expires header for static content in my web
application (technique described at
http://www.askapache.com/htaccess/apache-speed-expires.html).
I am using the HTTP Cache Manager in my test plan to simulate the
browser cache. From the documentation this component only supp
4 matches
Mail list logo