unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
	Daniel Mendler <mail@daniel-mendler.de>,
	emacs-devel@gnu.org
Subject: Re: [elpa] externals/marginalia 94fc7f0: README: Add ELPA badge
Date: Thu, 3 Jun 2021 19:07:29 +0300	[thread overview]
Message-ID: <YLj+QRxojYumRRHT@protected.localdomain> (raw)
In-Reply-To: <jwv8s3r6kx7.fsf-monnier+emacs@gnu.org>

* Stefan Monnier <monnier@iro.umontreal.ca> [2021-06-03 18:17]:
> >> Is there someone here with access to GNU ELPA's Apache configuration
> >> that would make a similar change?
> 
> I do have access, but it's been too many years since the last time
> I played with Apache's config, so I'd welcome some hand-holding.
> 
> >> If not, where should this request go?
> > I was about to suggest something along those lines, but it was not clear
> > to me that "no-cache" is sufficient to disable the aggressive caching.
> > I assume Stefan can adjust the Apache setting to serve *.svg files with
> > "no-cache" from the packages directory.
> 
> Any change we can use something less aggressive than `no-cache`,
> e.g. indicate that it should be considered stale after, say, 24h?

## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 day"
ExpiresByType image/jpeg "access plus 1 day"
ExpiresByType image/gif "access plus 1 day"
ExpiresByType image/png "access plus 1 day"
ExpiresByType text/css "access plus 1 day"
ExpiresByType application/pdf "access plus 1 day"
ExpiresByType text/x-javascript "access plus 1 day"
ExpiresByType application/x-shockwave-flash "access plus 1 day"
ExpiresByType image/x-icon "access plus 1 day"
ExpiresDefault "access plus 1 day"
</IfModule>
## EXPIRES CACHING ##



-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2021-06-03 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210530185719.10480.76043@vcs0.savannah.gnu.org>
     [not found] ` <20210530185720.C7394209BF@vcs0.savannah.gnu.org>
2021-05-30 19:56   ` [elpa] externals/marginalia 94fc7f0: README: Add ELPA badge Stefan Monnier
2021-05-31  4:56     ` Daniel Mendler
2021-05-31 13:18       ` Daniel Mendler
2021-05-31 14:27         ` Stefan Monnier
2021-06-03 14:42           ` Basil L. Contovounesios
2021-06-03 14:51             ` Daniel Mendler
2021-06-03 15:16               ` Stefan Monnier
2021-06-03 16:07                 ` Jean Louis [this message]
2021-06-03 23:12                 ` chad
2021-06-09 20:54                   ` Stefan Monnier
2021-06-09 21:41                     ` Basil L. Contovounesios
2021-06-10  0:19                     ` Jean Louis

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YLj+QRxojYumRRHT@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=contovob@tcd.ie \
    --cc=emacs-devel@gnu.org \
    --cc=mail@daniel-mendler.de \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).