[Seaside] [YSlow] How to set expires in response header for
cssand js resources?
ssastre at seaswork.com
Fri Aug 24 16:52:07 UTC 2007
In a quik test with this site that apache options represents 20% to
40% improvement in total load time with primed caches. Good enough for me
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Adrian Lienhard
> Enviado el: Viernes, 24 de Agosto de 2007 12:29
> Para: Seaside - general discussion
> Asunto: Re: [Seaside] [YSlow] How to set expires in response
> header for cssand js resources?
> On Aug 24, 2007, at 16:41 , Sebastian Sastre wrote:
> > To implement a systematic optimization like that we
> need to add the
> > expiry header for the css and the js files.
> > As they are inserted in the updateRoot: which is a
> process part of a
> > response that explicitely needs a cache control of "no
> cache" I don't
> > understand yet how we can set the expiration of only this two files
> > and not the rest of the html code. Can someone give me a glimpse on
> > how to achieve this?
> Apache has an expires module (see
> http://httpd.apache.org/docs/2.2/ mod/mod_expires.html),
> which allows you to set the expires header field for selected
> types of files. For example:
> ExpiresActive On
> ExpiresByType text/css "access plus 2 days"
> In my experience this has a noticeable effect on the page load time.
> Adrian Lienhard
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the seaside