Oops - my fault: browsers DO cache URLs with query strings, "so long
as freshness information is present"

(http://www.mnot.net/blog/2006/05/11/browser_caching)


On Feb 16, 4:59 pm, James Brady <[EMAIL PROTECTED]> wrote:
> Hi, thanks for that! I'll have a play.. It's a shame that this won't
> handle resources (e.g. images) referenced from CSS, but it's really
> the directly imported JS and CSS files that I was aiming for.
>
> Note that the original article suggested that the query string
> approach doesn't (or "shouldn't") work at 
> all:http://particletree.com/notebook/automatically-version-your-css-and-j...
>
> However, if it turns out that browser do cache URLs with query strings
> then this might be one care when non-standards compliant browsers
> actually help me!
>
> James
>
> On Feb 16, 6:27 am, Christopher Arndt <[EMAIL PROTECTED]> wrote:
>
> > Remi Jolin - SysGroup schrieb:
>
> > > le 16.02.2008 03:01 James Brady a écrit:
> > >> Hi, I'm researching the best way for me to dynamically add version
> > >> numbers to requested static files.
>
> > > what about adding the version number (or the update date) as a parameter
> > > of the URL like
> > >http://server/filename.xxxx?upd=200802161328(orany format of the
> > > update date you can get with the os library)
> > > So browsers will refresh the cache only if the parameter changes.
>
> > There's a recipe on the docs Wiki on how to do that automatically by
> > wrapping static resources in a widget, which adds the timestamp to the
> > URL, here:
>
> >http://docs.turbogears.org/1.0/WidgetsWithJSAndCSS#controlling-cachin...
>
> > Tiny URL:http://tinyurl.com/33xpxs
>
> > Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to