From publist.cr at gmail.com  Tue Mar 25 23:28:28 2025
From: publist.cr at gmail.com (C R)
Date: Wed, 26 Mar 2025 00:28:28 +0100
Subject: [RADIATOR] AuthREST issues
In-Reply-To: <CAHEFaoQ3+Yu0mKhVsv8dacg9eVqzxZkOJMXFxxDb0FK=Xes1uQ@mail.gmail.com>
References: <CAHEFaoQ3+Yu0mKhVsv8dacg9eVqzxZkOJMXFxxDb0FK=Xes1uQ@mail.gmail.com>
Message-ID: <CAD_Vsg0ovq0CCw5ZL+Tn-xwnLFQntxaiCdORWf=thC7Ri=fe_g@mail.gmail.com>

Hi Greg,

We have been runnig AuthBy REST for quite some time without any
special parameters (https to fast backends behind a reverse proxy).
Zero connection problems so far.

C.

Le mer. 5 f?vr. 2025 ? 18:46, Greg Haverkamp via radiator
<radiator at lists.open.com.au> a ?crit :
>
> I've been using AuthREST for a while to talk to a slowish HTTP backend.  (Before that, we used AuthURL and a worker farm.)
>
> We run our Radiator instances in containers, mostly on a single host.
>
> What we've witnessed is that, over time, the http connections become "stale", for lack of a better term.  They start preventing any outbound traffic, almost as if they're not recycled.  I can eliminate some of this by going to 1 Connection, and it wasn't until today that I realized we could go to 0.
>
> But mostly I'm wondering if others have seen this, if there are system settings that accommodate this better, etc.
>
> Greg
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator