From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: buildfarm server suddenly not talking to old SSL stacks? |
Date: | 2018-07-17 17:08:48 |
Message-ID: | 20180717170848.xxfbaywhot627aw7@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On 2018-Jul-17, Tom Lane wrote:
> doing the same thing the way the buildfarm script does it does not work:
>
> $ perl -MLWP::Simple -e 'LWP::Simple::getprint("http://buildfarm.postgresql.org/branches_of_interest.txt");'
> 500 Can't connect to buildfarm.postgresql.org:80 (No route to host) <URL:http://buildfarm.postgresql.org/branches_of_interest.txt>
I don't know if Varnish catches https calls as well as http, but if it
does, it could very well be related. A Varnish cache was added recently
to buildfarm.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2018-07-17 17:10:02 | Re: buildfarm server suddenly not talking to old SSL stacks? |
Previous Message | Tom Lane | 2018-07-17 17:04:50 | Re: buildfarm server suddenly not talking to old SSL stacks? |