computer-playbook/roles/web-app-seaweedfs/meta/server.yml at fix/dev-python/python-upper-bound - computer-playbook - Infinito.Nexus Code Hub

kevinveenbirkenbach/computer-playbook

0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 10:59:59 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 90ff555603 fix(seaweedfs): accept the SSO redirect on the api vhost

The api vhost has two branches in proxy.conf.j2: with SSO enabled it proxies
to the Keycloak SSO proxy, so an unauthenticated request is redirected; only
the else branch answers `return 403`. The expected status codes covered just
the second case, so the webserver health unit reported

  api.seaweedfs.s3.infinito.example: ERROR: Expected [403, 405]. Got 301.

and, because that unit grades the whole round, every deploy ended with
failed=1 while the applications themselves were fine.

The sibling endpoints already allow the redirect: filer and master both list
302 next to 403. Add 301 and 302 to api.

Not established: why api answers 301 where the siblings declare 302. A
permanent redirect may come from a slash or scheme normalisation ahead of the
SSO proxy rather than from the proxy itself; both codes are accepted here
instead of chasing that down.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-28 12:36:48 +02:00

15 lines

148 B

YAML

Raw Permalink Blame History

 ---
 client_max_body_size: 0
 status_codes:
   api:
     - 301
     - 302
     - 403
     - 405
   filer:
     - 302
     - 403
   master:
     - 302
     - 403