Every server pod gets INBUXA_HTTP_USE_FORWARDED=true. Its HTTP Service is only reached through the ingress or gateway and the webmail, and without this the server's sign-in bans and anonymous limits are charged to them. On kind with rc.31 behaviour, a proxy forwarding 110 different clients' failed sign-ins was banned after 101, which behind a real ingress means nobody can sign in on the web for 30 days.
server.trustedProxies (default empty: loopback and private ranges) sets INBUXA_HTTP_TRUSTED_PROXIES, for clusters whose pod network isn't private (100.64.0.0/10, say).
Tests: 2 new (63 in total). tools/check.sh passes.
An older server ignores the variable, so this can merge before rc.32. It takes effect when the chart's server image has the inbuxa-server change.
K-W3, chart side.
- Every server pod gets `INBUXA_HTTP_USE_FORWARDED=true`. Its HTTP Service is only reached through the ingress or gateway and the webmail, and without this the server's sign-in bans and anonymous limits are charged to them. On kind with rc.31 behaviour, a proxy forwarding 110 different clients' failed sign-ins was banned after 101, which behind a real ingress means nobody can sign in on the web for 30 days.
- `server.trustedProxies` (default empty: loopback and private ranges) sets `INBUXA_HTTP_TRUSTED_PROXIES`, for clusters whose pod network isn't private (100.64.0.0/10, say).
- Tests: 2 new (63 in total). `tools/check.sh` passes.
An older server ignores the variable, so this can merge before rc.32. It takes effect when the chart's server image has the inbuxa-server change.
INBUXA_HTTP_USE_FORWARDED=true on every server pod, so the server's limits
and bans for failed sign-ins and anonymous requests count each client, not
the ingress or the webmail. server.trustedProxies lists the proxies when
the pod network isn't a private range. Older servers ignore the variable.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-W3, chart side.
INBUXA_HTTP_USE_FORWARDED=true. Its HTTP Service is only reached through the ingress or gateway and the webmail, and without this the server's sign-in bans and anonymous limits are charged to them. On kind with rc.31 behaviour, a proxy forwarding 110 different clients' failed sign-ins was banned after 101, which behind a real ingress means nobody can sign in on the web for 30 days.server.trustedProxies(default empty: loopback and private ranges) setsINBUXA_HTTP_TRUSTED_PROXIES, for clusters whose pod network isn't private (100.64.0.0/10, say).tools/check.shpasses.An older server ignores the variable, so this can merge before rc.32. It takes effect when the chart's server image has the inbuxa-server change.