unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 37207@debbugs.gnu.org
Subject: bug#37207: guix.gnu.org Last Modified at epoch
Date: Wed, 28 Aug 2019 20:59:44 +0200	[thread overview]
Message-ID: <CAE4v=pj08reuetW6JC2+PA3TTZkyy17szVCYH=0THsytDnsdfg@mail.gmail.com> (raw)
In-Reply-To: <20190828170530.3a3d638e@scratchpost.org>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

Hello Danny,

Danny Milosavljevic <dannym@scratchpost.org> ezt írta (időpont: 2019. aug.
28., Sze, 17:05):

> Hi Gabor,
>
> On Wed, 28 Aug 2019 12:40:37 +0200
> Gábor Boskovits <boskovits@gmail.com> wrote:
>
> > Supressing the last modified header is just an
> > add_header Last-Modified "";
> > away.
> >
> > To get the info from the symlink seems to be much trickier, i would do
> with
> > either embedded perl or embedded lua. I am not sure if we should bother
> > with it, though. Wdyt?
>
> Since we already emit ETag, I don't think we need to bother with
> Last-Modified.
>
> Why is the ETag so short, though?
>
>
The ETag we emit is also bad. Nginx calculates this from mtime and
content-lenght,
so in our case it's just content length.


> >wget --debug -O /dev/null   https://guix.gnu.org/packages.json 2>&1 |
> grep -i etag
> >ETag: "1-2f38b1"
>
>
Best regards,
g_bor

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

[-- Attachment #2: Type: text/html, Size: 1985 bytes --]

  reply	other threads:[~2019-08-28 19:01 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
2019-09-26  8:39     ` Ludovic Courtès
2019-08-28 15:05   ` Danny Milosavljevic
2019-08-28 18:59     ` Gábor Boskovits [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to='CAE4v=pj08reuetW6JC2+PA3TTZkyy17szVCYH=0THsytDnsdfg@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=37207@debbugs.gnu.org \
    --cc=dannym@scratchpost.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).