Re: Spec ref cache headers

On Fri, Jan 6, 2017, at 23:40, Tab Atkins Jr. wrote:
> On Tue, Jan 3, 2017 at 2:01 AM, Tobie Langel <tobie@codespeaks.com>
> wrote:
> > On Tue, Jan 3, 2017, at 10:52, Marcos Caceres wrote:
> >> Hi All,
> >> We've updated Specref to serve cache-control HTTP headers. It now
> >> responds with e-tags and Expires headers set for 24 hours after
> >> request.
> >
> > Thanks Marcos, that's really cool!
> >
> > Tab, you might want to add a cache-busting param to Bikeshed update.
> 
> Why tho? At worst this means that updating Bikeshed will grab 24-hour
> old biblio data, which seems fine?  Let's not defeat caching unless
> necessary. ^_^

I was just thinking about the common scenario of editors needing to
re-build a spec after having updated some references in Specref.

--tobie

Received on Monday, 9 January 2017 10:09:11 UTC