Thread
-
faulty link
Erik Rijkers <er@xs4all.nl> — 2022-02-10T14:35:25Z
The provided link https://www.postgresql.org/docs/release/ leads to https://www.postgresql.org/docs/release/14.2/ which gives 'Not Found' for me (Netherlands) At least one person on IRC reports it 'works' for them but it seems there still something wrong.. Erik Rijkers
-
Re: faulty link
Josef Šimánek <josef.simanek@gmail.com> — 2022-02-10T14:48:29Z
It works well here (Czech republic). čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers <er@xs4all.nl> napsal: > > The provided link > https://www.postgresql.org/docs/release/ > > leads to > https://www.postgresql.org/docs/release/14.2/ > > which gives 'Not Found' for me (Netherlands) > > > At least one person on IRC reports it 'works' for them but it seems > there still something wrong.. > > > Erik Rijkers > > > > >
-
Re: faulty link
Wolfgang Walther <walther@technowledgy.de> — 2022-02-10T14:52:47Z
> leads to > https://www.postgresql.org/docs/release/14.2/ > > which gives 'Not Found' for me (Netherlands) Same here: Not Found. (Germany)
-
Re: faulty link
Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> — 2022-02-10T14:53:34Z
>The provided link > https://www.postgresql.org/docs/release/ >leads to > https://www.postgresql.org/docs/release/14.2/ >which gives 'Not Found' for me (Netherlands) Works fine for me in Germany Regards Daniel
-
Re: faulty link
Josef Šimánek <josef.simanek@gmail.com> — 2022-02-10T14:54:42Z
čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers <er@xs4all.nl> napsal: > > The provided link > https://www.postgresql.org/docs/release/ > > leads to > https://www.postgresql.org/docs/release/14.2/ > > which gives 'Not Found' for me (Netherlands) Thinking about that again, the 14.2 release just happened. Could it be just a matter of propagating new release info to mirrors? > > At least one person on IRC reports it 'works' for them but it seems > there still something wrong.. > > > Erik Rijkers > > > > >
-
Re: faulty link
Tom Lane <tgl@sss.pgh.pa.us> — 2022-02-10T15:23:45Z
=?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= <josef.simanek@gmail.com> writes: > čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers <er@xs4all.nl> napsal: >> The provided link >> https://www.postgresql.org/docs/release/ >> leads to >> https://www.postgresql.org/docs/release/14.2/ >> which gives 'Not Found' for me (Netherlands) > Thinking about that again, the 14.2 release just happened. Could it be > just a matter of propagating new release info to mirrors? The link works for me, too (USA). Stale cache seems like a reasonable explanation for the OP's problem --- maybe clearing browser cache would help? regards, tom lane
-
Re: faulty link
Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> — 2022-02-10T15:53:02Z
Tom Lane <tgl@sss.pgh.pa.us> writes: > =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= <josef.simanek@gmail.com> writes: >> čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers <er@xs4all.nl> napsal: >>> The provided link >>> https://www.postgresql.org/docs/release/ >>> leads to >>> https://www.postgresql.org/docs/release/14.2/ >>> which gives 'Not Found' for me (Netherlands) > >> Thinking about that again, the 14.2 release just happened. Could it be >> just a matter of propagating new release info to mirrors? > > The link works for me, too (USA). Stale cache seems like a reasonable > explanation for the OP's problem --- maybe clearing browser cache > would help? I'm getting a 404 as well from London. After trying multiple times with curl I did get one 200 response, but it's mostly 404s. It looks like some of the mirrors have it, but not all: $ for h in $(dig +short -tA www.mirrors.postgresql.org); do echo -n "$h: "; curl -i -k -s -HHost:www.postgresql.org "https://$h/docs/release/14.2/" | grep ^HTTP; done 72.32.157.230: HTTP/2 200 87.238.57.232: HTTP/2 404 217.196.149.50: HTTP/2 200 $ for h in $(dig +short -tAAAA www.mirrors.postgresql.org); do echo -n "$h: "; curl -i -k -s -HHost:www.postgresql.org "https://[$h]/docs/release/14.2/" | grep ^HTTP; done 2001:4800:3e1:1::230: HTTP/2 200 2a02:c0:301:0:ffff::32: HTTP/2 404 2a02:16a8:dc51::50: HTTP/2 200 > regards, tom lane - ilmari
-
Re: faulty link
Dave Page <dpage@pgadmin.org> — 2022-02-10T16:07:18Z
On Thu, 10 Feb 2022 at 15:53, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> wrote: > Tom Lane <tgl@sss.pgh.pa.us> writes: > > > =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= <josef.simanek@gmail.com> writes: > >> čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers <er@xs4all.nl> napsal: > >>> The provided link > >>> https://www.postgresql.org/docs/release/ > >>> leads to > >>> https://www.postgresql.org/docs/release/14.2/ > >>> which gives 'Not Found' for me (Netherlands) > > > >> Thinking about that again, the 14.2 release just happened. Could it be > >> just a matter of propagating new release info to mirrors? > > > > The link works for me, too (USA). Stale cache seems like a reasonable > > explanation for the OP's problem --- maybe clearing browser cache > > would help? > > I'm getting a 404 as well from London. After trying multiple times with > curl I did get one 200 response, but it's mostly 404s. > > It looks like some of the mirrors have it, but not all: > > $ for h in $(dig +short -tA www.mirrors.postgresql.org); do echo -n "$h: > "; curl -i -k -s -HHost:www.postgresql.org "https://$h/docs/release/14.2/" > | grep ^HTTP; done > 72.32.157.230: HTTP/2 200 > 87.238.57.232: HTTP/2 404 > 217.196.149.50: HTTP/2 200 > > $ for h in $(dig +short -tAAAA www.mirrors.postgresql.org); do echo -n > "$h: "; curl -i -k -s -HHost:www.postgresql.org "https://[$h]/docs/release/14.2/" > | grep ^HTTP; done > 2001:4800:3e1:1::230: HTTP/2 200 > 2a02:c0:301:0:ffff::32: HTTP/2 404 > 2a02:16a8:dc51::50: HTTP/2 200 > Despite the name, they're not actually mirrors. They're varnish caches. By the looks of it one of them cached a 404 (probably someone tried to access the new page before it really did exist). I've purged /docs/release now, and everything is returning 200. -- Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com