git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v7 1/4] gitweb: Move check-ref-format code into separate function

From
Krzesimir Nowak <krzesimir@endocode.com>
Date
Dec 11, 2013, 11:54 UTC
Message-ID
<1386762884-7564-2-git-send-email-krzesimir@endocode.com>
In-Reply-To
<1386762884-7564-1-git-send-email-krzesimir@endocode.com>
This check will be used in more than one place later.
Signed-off-by: Krzesimir Nowak <krzesimir@endocode.com>
---
 gitweb/gitweb.perl | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 68c77f6..46bd6ac 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -1452,6 +1452,16 @@ sub validate_pathname {
 	return $input;
 }
 
+sub is_valid_ref_format {
+	my $input = shift || return undef;
+
+	# restrictions on ref name according to git-check-ref-format
+	if ($input =~ m!(/\.|\.\.|[\000-\040\177 ~^:?*\[]|/$)!) {
+		return undef;
+	}
+	return $input;
+}
+
 sub validate_refname {
 	my $input = shift || return undef;
 
@@ -1462,10 +1472,9 @@ sub validate_refname {
 	# it must be correct pathname
 	$input = validate_pathname($input)
 		or return undef;
-	# restrictions on ref name according to git-check-ref-format
-	if ($input =~ m!(/\.|\.\.|[\000-\040\177 ~^:?*\[]|/$)!) {
-		return undef;
-	}
+	# check git-check-ref-format restrictions
+	is_valid_ref_format($input)
+		or return undef;
 	return $input;
 }
 
-- 
1.8.3.1
Previous: Krzesimir NowakNext: Krzesimir Nowak
Message 2 of 7 in “Show extra branch refs in gitweb”
  1. 0/4 Show extra branch refs in gitwebKrzesimir Nowak, Dec 11, 2013
  2. 1/4 gitweb: Move check-ref-format code into separate functionKrzesimir Nowak, Dec 11, 2013
  3. 2/4 gitweb: Return 1 on validation success instead of passed inputKrzesimir Nowak, Dec 11, 2013
  4. Jakub NarębskiDec 11, 2013
  5. 3/4 gitweb: Add a feature for adding more branch refsKrzesimir Nowak, Dec 11, 2013
  6. 4/4 gitweb: Denote non-heads, non-remotes branchesKrzesimir Nowak, Dec 11, 2013
  7. Junio C HamanoDec 12, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.