From: "Ludovic Courtès" <ludo@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 37207@debbugs.gnu.org
Subject: bug#37207: guix.gnu.org Last Modified at epoch
Date: Thu, 05 Sep 2019 22:47:36 +0200 [thread overview]
Message-ID: <875zm6eahj.fsf@gnu.org> (raw)
In-Reply-To: <87ftlki1qr.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 29 Aug 2019 14:40:12 +0200")
Hello!
Did one of you have chance to come up with a trick to emit the right
‘Last-Modified’? We seemed to be close to having something. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-09-05 20:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 9:52 bug#37207: guix.gnu.org returns Last-Modified = Epoch Ludovic Courtès
2019-08-28 10:40 ` bug#37207: guix.gnu.org Last Modified at epoch Gábor Boskovits
2019-08-28 14:37 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-08-28 19:42 ` Gábor Boskovits
2019-08-28 20:32 ` Ludovic Courtès
2019-08-29 6:11 ` Gábor Boskovits
2019-08-29 12:40 ` Ludovic Courtès
2019-09-05 20:47 ` Ludovic Courtès [this message]
2019-09-26 8:39 ` Ludovic Courtès
2019-08-28 15:05 ` Danny Milosavljevic
2019-08-28 18:59 ` Gábor Boskovits
2020-03-26 23:06 ` bug#37207: nginx serving files from the store returns Last-Modified = Epoch Vincent Legoll
2020-03-29 9:50 ` Gábor Boskovits
2020-03-30 11:53 ` Vincent Legoll
2020-03-26 23:30 ` bug#37207: Repology Vincent Legoll
2020-05-09 22:07 ` bug#37207: guix.gnu.org returns Last-Modified = Epoch Christopher Baines
2020-05-10 10:11 ` Ludovic Courtès
2020-05-11 10:32 ` Christopher Baines
2020-05-11 12:47 ` Ludovic Courtès
2020-05-25 8:24 ` Christopher Baines
2020-05-25 8:20 ` bug#37207: [PATCH] nginx: berlin: Work around Last-Modified issues for guix.gnu.org Christopher Baines
2020-05-15 21:12 ` bug#37207: nginx serving files from the store returns Last-Modified = Epoch anadon via web
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=875zm6eahj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37207@debbugs.gnu.org \
--cc=boskovits@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.