| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:10:31 |
| Message-ID: | CABUevEzVM4vodr=0hCch0X7kZAtCiXiRJezpOzzHSNGUg63hZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, Jul 17, 2018 at 7:08 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> 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.
>
>
https is terminated in haproxy and relayed from there. Varnish doesn't
speak native https.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-17 17:29:01 | Re: buildfarm server suddenly not talking to old SSL stacks? |
| Previous Message | Magnus Hagander | 2018-07-17 17:10:02 | Re: buildfarm server suddenly not talking to old SSL stacks? |