From: Tom Tromey <tom@tromey.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH htdocs] css: add content hash to force refreshes as needed
Date: Fri, 15 Dec 2023 09:12:40 -0700 [thread overview]
Message-ID: <87wmtf78cn.fsf@tromey.com> (raw)
In-Reply-To: <20231215025857.27816-1-vapier@gentoo.org> (Mike Frysinger's message of "Thu, 14 Dec 2023 21:58:57 -0500")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Mike> Browsers will cache CSS files (a good thing), but we need to make sure
Mike> they refetch when the file changes, vs eventually expiring. Add the
Mike> file hash to the query string so browsers refetch automatically.
Seems like a good idea. Thank you.
Tom
prev parent reply other threads:[~2023-12-15 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 2:58 Mike Frysinger
2023-12-15 16:12 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmtf78cn.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).