From unknown Sat Jun 21 10:42:15 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#58895 <58895@debbugs.gnu.org> To: bug#58895 <58895@debbugs.gnu.org> Subject: Status: GNU ELPA: Stale badges in GitHub cache Reply-To: bug#58895 <58895@debbugs.gnu.org> Date: Sat, 21 Jun 2025 17:42:15 +0000 retitle 58895 GNU ELPA: Stale badges in GitHub cache reassign 58895 emacs submitter 58895 Stefan Kangas severity 58895 minor thanks From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 30 10:59:47 2022 Received: (at submit) by debbugs.gnu.org; 30 Oct 2022 14:59:47 +0000 Received: from localhost ([127.0.0.1]:38831 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1op9mt-0005Fn-73 for submit@debbugs.gnu.org; Sun, 30 Oct 2022 10:59:47 -0400 Received: from lists.gnu.org ([209.51.188.17]:32966) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1op9ms-0005Fg-4J for submit@debbugs.gnu.org; Sun, 30 Oct 2022 10:59:46 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1op9mr-000308-P8 for bug-gnu-emacs@gnu.org; Sun, 30 Oct 2022 10:59:45 -0400 Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1op9mq-0005sO-6a for bug-gnu-emacs@gnu.org; Sun, 30 Oct 2022 10:59:45 -0400 Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-13ae8117023so11244353fac.9 for ; Sun, 30 Oct 2022 07:59:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=BnJiWM9qElkjRsuMCC7PtqKjOoCp7d70h91OhfKMAjA=; b=MVv37wNvnACGQ62VD3C8bQFCmDjZbKnQeNcd9quJXPBCbD9s9N4EDMUqFl0pRpMc8/ +L//zpm2GRvuy6xOFIRXzxKZHkiCxmgzPLzlep9EyodgukdNfb7W2TYfyoCZzXLHMqme KAGuveXFwbeSQfZ7KslMhQl7NtL2iIWhuuhJ0x8YXLXS68208ztH7p3d77HHtrZ4mHZL QyIjm+zG9sXluQgRMRkL93oEDJBBYDr9qPKlmMpU7zWgjrutcL0lzBh8wKxwIUgXCNJn Wh9E9OSyCxzn++S+bUCN8goTw2BcSRnWq3VTtP75olVona6Xn5kgTDnLkxgPHpI1jEO4 KykQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BnJiWM9qElkjRsuMCC7PtqKjOoCp7d70h91OhfKMAjA=; b=0dZej2yK4LYtgrpstuIcEHcbMQ2ViKkxk2NHME1QXxv9gu7czAdvR7kYFJsRhCfEbd UcHZhXzqApkOFmMkaxi51lB52/DaERpuCDCVtA44pgoiGaD/21Pn32aA2ZZiPgLbWKtw W9TbssCD3xh4jTGoEgvBFyZ34kPPOG00dlwTNNEpNKnqxf8XCufPQ5xUkXyZpjiAuZ5l Z8QYA99aN8FcFkqGy3oykgQRctIzmKRJY+LAkVd1c7X6Xy6VgeIzkKG5YVhx49s90L32 avJB/jpMlrKCUwd+4HjlQaJk+EEj7M5oG/1fooErNOxJe/vq84LiJWvXsAg3+Rgfzztd KvpQ== X-Gm-Message-State: ACrzQf2D6zVKegtwOf3jvMC5jyCcCRnOFocZV2dFR/wbXoR5AY2DL8le 2VYFieZQCLvqCmjG8X1+8UyksxrvJD7ZskeebrS/ULNe X-Google-Smtp-Source: AMsMyM6LO9pcpEM9r6kI1SDXm7/bo6SnS3M3BuVH3n1GndV7mbQpp/9L1MENsthzFyBPXH30EP5ISZTKYoLJhRbUJMc= X-Received: by 2002:a05:6870:d79a:b0:136:50d7:faa9 with SMTP id bd26-20020a056870d79a00b0013650d7faa9mr14117841oab.92.1667141982627; Sun, 30 Oct 2022 07:59:42 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sun, 30 Oct 2022 07:59:42 -0700 From: Stefan Kangas X-Debbugs-CC: Stefan Monnier X-Hashcash: 1:20:221030:bug-gnu-emacs@gnu.org::wPCeY5wanZi6ozMr:63IQ MIME-Version: 1.0 Date: Sun, 30 Oct 2022 07:59:42 -0700 Message-ID: Subject: GNU ELPA: Stale badges in GitHub cache To: bug-gnu-emacs@gnu.org Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=2001:4860:4864:20::35; envelope-from=stefankangas@gmail.com; helo=mail-oa1-x35.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.3 (-) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) Severity: minor I often see stale badges in the GitHub cache, sometimes for several days. I think we should use a "Cache-Control" header when serving them: $ curl -i https://elpa.gnu.org/packages/url-scgi.svg HTTP/1.1 200 OK Date: Sun, 30 Oct 2022 14:45:24 GMT Server: Apache/2.4.54 (Debian) Last-Modified: Sat, 29 Oct 2022 21:04:31 GMT ETag: "4c2-5ec32b879e704" Accept-Ranges: bytes Content-Length: 1218 Content-Type: image/svg+xml [...] Here, we should also have: Cache-Control: max-age=21600, must-revalidate This should ensure that they are only ever cached for 12 hours, which roughly coincides with how often we update the archive. Probably something like this in .htaccess should suffice: Header unset Cache-Control Header set Cache-Control "max-age=21600, must-revalidate" For more, see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control https://httpd.apache.org/docs/2.4/mod/core.html#filesmatch From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 30 11:22:12 2022 Received: (at 58895) by debbugs.gnu.org; 30 Oct 2022 15:22:12 +0000 Received: from localhost ([127.0.0.1]:38839 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1opA8a-0005oS-Bn for submit@debbugs.gnu.org; Sun, 30 Oct 2022 11:22:12 -0400 Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:14322) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1opA8X-0005oD-IH for 58895@debbugs.gnu.org; Sun, 30 Oct 2022 11:22:10 -0400 Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 7F80380325; Sun, 30 Oct 2022 11:22:03 -0400 (EDT) Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1969780223; Sun, 30 Oct 2022 11:21:58 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1667143318; bh=QoOfX/EGyHj1slPd0tcYARrGZpVL4E7SdrJCze5darE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Z2gWdebT8FpCK9E/oaHcsHnT4d0C+9ySH00gQWw03qT86oWvVVvTB4wNnoBYWn9QO qNKAaoxwN5sJMgFKEMM3HS9LwDrNG+SoDgpkBVTbomyvhTOULAh3NsKfdSmD30LTkC bOpCNidHe57iXpX/jjejFwqwqBuSVTZQR2DMKPx922pY6Acky2Ghkk9e901PBh7f5t w1DMPpRj61+vLVZZcWtpiRswwbAj1R5Ycy8M7vCXfVkuENnlGPwJW0a1GvPTbUFTue reF/48ZVUexy7EwpQEA1haDqMLsalEHTlav7Oo+xljSMkaVpo0lJPO0hwaNf2/15Wc m1Rq6T8x7hRUQ== Received: from pastel (65-110-220-202.cpe.pppoe.ca [65.110.220.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id E2BFE120F15; Sun, 30 Oct 2022 11:21:57 -0400 (EDT) From: Stefan Monnier To: Stefan Kangas Subject: Re: bug#58895: GNU ELPA: Stale badges in GitHub cache In-Reply-To: (Stefan Kangas's message of "Sun, 30 Oct 2022 07:59:42 -0700") Message-ID: References: Date: Sun, 30 Oct 2022 11:21:56 -0400 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SPAM-INFO: Spam detection results: 0 ALL_TRUSTED -1 Passed through trusted hosts only via SMTP AWL -0.006 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain X-SPAM-LEVEL: X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58895 Cc: 58895@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > I often see stale badges in the GitHub cache, sometimes for several > days. I think we should use a "Cache-Control" header when serving them: Hmm... we had a directive for that in Apache's config, but it wasn't quite right. It should be working now. It uses slightly different settings. You said "12 hours", your code sais 6 hours, and the code we had used 24 hours. I kept the 24 hours. Your code said "must-revalidate", the code we had (and still have) said/says "public". I think public is right, but I don't really know what "must-revalidate" (or its lack) implies. Stefan From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 30 11:46:22 2022 Received: (at 58895-done) by debbugs.gnu.org; 30 Oct 2022 15:46:22 +0000 Received: from localhost ([127.0.0.1]:38864 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1opAVy-0006PW-37 for submit@debbugs.gnu.org; Sun, 30 Oct 2022 11:46:22 -0400 Received: from mail-oa1-f53.google.com ([209.85.160.53]:42800) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1opAVw-0006PH-D5 for 58895-done@debbugs.gnu.org; Sun, 30 Oct 2022 11:46:20 -0400 Received: by mail-oa1-f53.google.com with SMTP id 586e51a60fabf-13ae8117023so11311624fac.9 for <58895-done@debbugs.gnu.org>; Sun, 30 Oct 2022 08:46:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=PjhsI40q6kK/gXNrO8A62Gr4JVUmrxLOBWU/bGyqULQ=; b=O8xHFGUOk1lj+8miwvmrFtrOZVeb9birX9lPKtWwyMIf4KT+yyJJvPL1jJgTr2y0cP uls3XClPStqfHJyPVIuYIdYZW1VUXaOPyZAa/vQ2FrEtDrVAR0xTddqFYmPtulDPpOSQ zeRzXQeV94GLLF3zevFvPdfnY6uiJRPFSTuVjfloae1gkdVxqmnBdz088FbSENx/+TCw IBylqg+S8Nvgx85AORXvgrIEyTuNMxBEHT0J+rDoI2dzw4EPuwVNjAKWd6pymlTfxt91 P5FljdvOwK4fioYHHc5TxM11wr9idFX4PJo7EnqWOu36+5cEChvcRWwglq81tO8Ay7yj +Qqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=PjhsI40q6kK/gXNrO8A62Gr4JVUmrxLOBWU/bGyqULQ=; b=uqwrGKtJTgtqr+T9fvAGh0ikBkYYZQpJxzgU9bH3bQ9KCgQMVVuWCP4d4hegL3L8q0 bJOuAR+d5pLWlHLWR/OEKoVO0kByYu9nlvX/djYjpQe9bTMcBN7WiU1tE6Edt4IJnqNb aLCisaETJGBFZa2MqPSUhuPnLWns7J9r7Zc0yEh5apqsE1DApHTMUEDoMqx1RHFpv/Py Za0XbdXmrq4Yyms7NMEUWnWT9UMt8lPmXzgDbY0EGuSrd8NOoYyd6s835devhnMe6qpE 4C2Av5U/4xjgtZ9M72PvCVXyV+Orrk9pFSotAIvN/I1RBbgetkuSN05bJCZ3OK/11b+C 0/4w== X-Gm-Message-State: ACrzQf0yTnR/5pzf6Y7ZhRJshx3pvhVM1VBdaSBItWaI+IYSHVTlNfEZ ZtOnHzZM9Zcpp5PGjLxbidPoh8IvpMvk+7H2gjE= X-Google-Smtp-Source: AMsMyM6WmdeYD1WYb8E5eyAob+dQ+3ft/7fuXWr6B8zvaTIyTP7xBcGZE+9CAoW5vKYEBfaNv+twfuReCnGb/vy98RM= X-Received: by 2002:a05:6870:d79a:b0:136:50d7:faa9 with SMTP id bd26-20020a056870d79a00b0013650d7faa9mr14224278oab.92.1667144774729; Sun, 30 Oct 2022 08:46:14 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sun, 30 Oct 2022 08:46:14 -0700 From: Stefan Kangas In-Reply-To: References: X-Hashcash: 1:20:221030:58895-done@debbugs.gnu.org::gXFQRCrco1CnSmU4:1dlF MIME-Version: 1.0 Date: Sun, 30 Oct 2022 08:46:14 -0700 Message-ID: Subject: Re: bug#58895: GNU ELPA: Stale badges in GitHub cache To: Stefan Monnier Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58895-done Cc: 58895-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Stefan Monnier writes: > Hmm... we had a directive for that in Apache's config, but it wasn't > quite right. It should be working now. > It uses slightly different settings. > You said "12 hours", your code sais 6 hours, and the code we had used > 24 hours. I kept the 24 hours. Sounds good, thanks. > Your code said "must-revalidate", the code we had (and still have) > said/says "public". I think public is right, but I don't really know > what "must-revalidate" (or its lack) implies. >From reading the docs, "public" should be fine. From unknown Sat Jun 21 10:42:15 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Mon, 28 Nov 2022 12:24:09 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator