auth: CallerMiddleware header priority order is undocumented #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CallerMiddlewarechecksX-Auth-Request-Userfirst, then falls back toX-Forwarded-User. If a future auth proxy sets both headers (e.g. oauth2-proxy in some configs does), behaviour is undefined and untested.File:
internal/auth/caller.go:10-18Suggestions: