On Wed, Apr 12, 2023 at 9:27 AM Andrei Borzenkov
wrote:
> On Tue, Apr 11, 2023 at 6:27 PM Ken Gaillot wrote:
> >
> > On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> > > I fixed the issue by changing location definition from:
> > >
> > > location intranet-ip_on_any_nginx intranet-ip \
> >
On Tue, Apr 11, 2023 at 6:27 PM Ken Gaillot wrote:
>
> On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> > I fixed the issue by changing location definition from:
> >
> > location intranet-ip_on_any_nginx intranet-ip \
> > rule -inf: opa-nginx_1_active eq 0 \
> > rule -inf:
This is a multipart message in MIME format.
Rq39EWBVFo_related
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Type: multipart/related;
boundary="--Rq39EWBVFo_related" charset="utf-8"
It does not matter if ip resource starts on n=
On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> I fixed the issue by changing location definition from:
>
> location intranet-ip_on_any_nginx intranet-ip \
> rule -inf: opa-nginx_1_active eq 0 \
> rule -inf: opa-nginx_2_active eq 0
>
> To:
>
> location
I fixed the issue by changing location definition from:
location intranet-ip_on_any_nginx intranet-ip \
rule -inf: opa-nginx_1_active eq 0 \
rule -inf: opa-nginx_2_active eq 0
To:
location intranet-ip_on_any_nginx intranet-ip \
rule opa-nginx_1_active eq 1 \
