However, browsers cache on EXACT URLs. So if you attach ?2010011023 to a URL, it will only be valid until the URL changes or the expiry time comes around. Darren L. VanBuren ===================== http://theoks.net/ On Fri, Jan 8, 2010 at 17:13, Toshio Kuratomi <a.badger@xxxxxxxxx> wrote: > On Fri, Jan 08, 2010 at 10:42:35AM -0800, Darren VanBuren wrote: >> On the matter of Expires, here's what would need to be added to an >> Apache config, assuming static stuff is in /srv/web/static: >> >> <Directory /srv/web/static> >> ExpiresByType image/gif "access plus 1 month" >> ExpiresByType image/png "access plus 1 month" >> ExpiresByType text/css "access plus 1 month" >> ExpiresByType text/javascript "access plus 1 month" >> </Directory> >> >> Of course we can tweak the times, I just made up 1 month. >> > Is this how Expires work? :: > > * Client requests fp.o/static/fedora.css > * Client receives fedora.css with an Expires line of 1 month > * For the next month, the client does not retrieve new versions of > fedora.css. > > If so, we're either going to want to keep the Expires time pretty low (an > hour or less) or start adding version information into all of our static > resources. > > -Toshio > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list > _______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
