From 4510aa679ad069346a6aeff5729f78cdf9cc65a5 Mon Sep 17 00:00:00 2001
From: iTrooz <hey@itrooz.fr>
Date: Sat, 4 Oct 2025 08:10:49 +0200
Subject: [PATCH] docs: fix variants of --user-from-header

---
 lib/http/auth.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/http/auth.go b/lib/http/auth.go
index 6fead3827..babd91163 100644
--- a/lib/http/auth.go
+++ b/lib/http/auth.go
@@ -20,7 +20,7 @@ You can either use an htpasswd file which can take lots of users, or
 set a single username and password with the ` + "`--{{ .Prefix }}user` and `--{{ .Prefix }}pass`" + ` flags.
 
 Alternatively, you can have the reverse proxy manage authentication and use the
-username provided in the configured header with ` + "`--user-from-header`" + `  (e.g., ` + "`--{{ .Prefix }}--user-from-header=x-remote-user`" + `).
+username provided in the configured header with ` + "`--user-from-header`" + `  (e.g., ` + "`--{{ .Prefix }}user-from-header=x-remote-user`" + `).
 Ensure the proxy is trusted and headers cannot be spoofed, as misconfiguration
 may lead to unauthorized access.