Re: [Tools-discuss] moving/marking rfcdiff to not get cached by cloudflare

[Henrik Levkowetz <[e-mail]>]

Inline:

On 2020-01-02 03:41, Glen wrote:
> On Wed, Jan 1, 2020 at 6:29 PM Martin Thomson <[e-mail]> wrote:
>> On Wed, Jan 1, 2020, at 07:14, Michael Richardson wrote:
>> > I construct URLs for rfcdiff, pointing it to my formatted txt file on github,
>> > against my DT -XX.txt file. This is now being cached, I assume by
>> > cloudflare.
>> > Being able to Shift-Reload on the tab to validate the changes is really useful.
>> > I wonder if we can someone how mark the results as uncacheable?
>> > Or move rfcdiff to another name which isn't cached? or...?
> 
> Hi Michael -
> 
> Sorry if I'm missing a detail, but I'm not sure whether you're using
> the IETF rfcdiff (www.ietf.org/rfcdiff) or whether you're using
> Henrik's Tools servers (tools.ietf.org/rfcdiff) .  I can of course
> only speak for the former.  If you're on www.ietf.org, I have reviewed
> the Cloudflare configuration, and I can tell you that:
> 
> www.ietf.org/rfcdiff/*
> www.ietf.org/tools/*
> 
> are both *NOT* cached.  That is to say Cloudflare is configured to
> always pass those things through to our server without caching or
> storage.
> 
>> Shift-Reload should mark the request as not drawing from cache.  But the response I see doesn't have any validity information.  That might mean that you might be getting heuristic caching.
>> That said, after testing this on [1], the time spent waiting (almost 3s) seems to indicate that no cache is involved.  A simple reload was enough to induce that delay, not the cache-busting shift-reload.  In this case, that means setting Cache-Control: max-age=0 on the request, which seems to be enough.
> 
> +1
> 
>> [1] https://tools.ietf.org/rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-git-using-github.txt&url2=https://ietf-gitwg.github.io/using-github/draft-ietf-git-using-github.txt
> 
> If, however, you are, as Martin is, using tools.ietf.org, then we'll
> need to wait for Henrik to get back (I believe on the 6th) for him to
> comment.

tools.ietf.org is not behind a CDN, and there is no caching going on.

> And, of course, the *sources* of your txt files might be cached on
> their end - I have no idea, for example, what github might be doing...

That could indeed be the issue.

	Henrik

> Glen
> --
> Glen Barney
> IT Director
> AMS (IETF Secretariat)
> 
> ___________________________________________________________
> Tools-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to [e-mail]
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to [e-mail]
>