Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um3If-009EXz-Et for pgsql-www@arkaria.postgresql.org; Wed, 13 Aug 2025 04:41:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1um3Id-00BxyT-IQ for pgsql-www@arkaria.postgresql.org; Wed, 13 Aug 2025 04:41:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um3Id-00BxyL-C9 for pgsql-www@lists.postgresql.org; Wed, 13 Aug 2025 04:41:19 +0000 Received: from mail-lj1-x234.google.com ([2a00:1450:4864:20::234]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1um3Ib-000Im7-0m for pgsql-www@postgresql.org; Wed, 13 Aug 2025 04:41:18 +0000 Received: by mail-lj1-x234.google.com with SMTP id 38308e7fff4ca-3322a34e84fso53052931fa.0 for ; Tue, 12 Aug 2025 21:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755060076; x=1755664876; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=LaGSxiifggt9B6rQx1FpvJRo/jbq8GJWkJVcFPV9Sug=; b=QnhpFGhz8GKTpjA9hjvE+8j62iCYG3UBYC6ycUPT3KZq/W5KgRPZQ7KGErJNz38NLB jqWlrjY9MeYxxG4p327HNOuMR0ExcCsjCkFCnFflDViZOrNDafN2iFbuS+WjNz2ll+Ib 9SygEvTijWWhknJuYHguV5bWblwiszRTHH/yoss6B/6gAbVm3BbvtAnuFKxWCdxdUw+p r/Ot5jZGq6d9ziAHvkKttcBdu13aG4lvfAeLjZdZ55RjcGnUNpevwr7WpjOmRgqsMyeR djvOBCz4GT4GvfZWna9BGskVoXX6FlP4TnwSaGDc5zo3uL9JDwYDGfR2MRBoKM+FFDA8 pi6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755060076; x=1755664876; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=LaGSxiifggt9B6rQx1FpvJRo/jbq8GJWkJVcFPV9Sug=; b=AMICV2laBjBDCWBrSUYux6ly8t2zy7+fXytADlwG/cEQfXyiy1nl8sYu1GVBAOhDnd oKiijyEV3S2JOK5eavodraNbLakXQPDnkIzSGmkjLCpbURq7HJ4TZ5jYhjNVUeowlBe6 dqSerOng8AZrYnwNN1+B+WA1ggUUpRd8pWR/YagvnG31WzSUIU+jFo6K61Hk/8vnjaOC vM3WToEABZjynXBw4WV8XD6Ba6g4En6p5Dd9ZVt2LdFIhblpKT+wwZa7bsurknGcf01Y oRm0+MS+kfOSfvpV4sEx6Di5NrEbYxnsjrrl0C5U1xF27jwxfbQ+tKLHIusgRhn4qqjw xfZQ== X-Gm-Message-State: AOJu0YwubHfBB2RgJ1c4q7bJ8PZHPa5VKAUShAK7oUdUK//AgAxZSCfE LrLDJQC8j/SYQRl7mDAOwWf14M0KmsniFEJ3g29Qe87uPkh5Ibvq1qDmFcgTMkNXs0sOlvhsA1C 5LqnV7UQmkO8oNbSeLpc8j/DR9yJ5vMdmTgCegdw= X-Gm-Gg: ASbGncsBvQ8jDrBETPXUTP5gSfVPRevEv2SfGHgMm88QSm/GJl5vm4WumqIMTUmD8S9 +eRrSSa0sbqm9S1Ociu2Z+3x5SF88QFvQU7qtihe9XjyUpLGO13lamYzL96XmSm5y0gX7o7og/y RUMfXz0GBbtgGvJpR8d4jThDOdwhsYUXFlx0XjeLD+qG4D/wg3WFkkM+GrhI5mCP8wrxtAdQsKL sjAsYyx X-Google-Smtp-Source: AGHT+IG+a6+TowYzWGnTIWNi5hVciJ5mmiQoEkgWIuHuLTVwTJ0AbZDCWAf3ar0BS3ldjZri8fgr4oxH7fisa7lp4UU= X-Received: by 2002:a2e:b8c9:0:b0:333:7e57:67f0 with SMTP id 38308e7fff4ca-333e9b40875mr4287171fa.28.1755060075584; Tue, 12 Aug 2025 21:41:15 -0700 (PDT) MIME-Version: 1.0 From: Chris Bandy Date: Tue, 12 Aug 2025 23:41:03 -0500 X-Gm-Features: Ac12FXwrfMz7ADjXDQv9StAmGdNMFmU5EkTdePrXiooFEEtdcsZYeriMdH32zC4 Message-ID: Subject: Unable to browse blobs on gitweb To: pgsql-www@postgresql.org Content-Type: multipart/alternative; boundary="0000000000005d6111063c37c4a7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005d6111063c37c4a7 Content-Type: text/plain; charset="UTF-8" Hello! I like to link to the Postgres source code and comments in my extension code comments. I use https://git.postgresql.org/gitweb for that, as it seems to be the canonical site for Postgres source code. Lately, I have encountered HTTP 429 errors when trying to access blobs. For example, curl -I ' > https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=HISTORY' > HTTP/2 429 > date: Wed, 13 Aug 2025 04:29:33 GMT > server: Varnish > x-varnish: 1288456 > retry-after: 300 > content-length: 0 Is this intentional? If so, is there a better domain or site to (roughly) permalink to specific lines of released Postgres code? Thanks! -- Chris --0000000000005d6111063c37c4a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello!

I like to link to the Postgres s= ource code and comments in my extension code comments. I use https://git.postgresql.org/gitweb for t= hat, as it seems to be the canonical site for Postgres source code.

Lately, I have encountered HTTP 429 errors when trying to= access blobs. For example,

curl -I 'ht= tps://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dblob;f=3DHISTORY'
HTTP/2 429
date: Wed, 13 Aug 2025 04:29:33 GMT
server: Var= nish
x-varnish: 1288456
retry-after: 300
content-length: 0<= /blockquote>

Is this intentional? If so, is there a bett= er domain or site to (roughly) permalink to specific lines of released Post= gres code?

Thanks!

-- Chr= is
--0000000000005d6111063c37c4a7--