From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 1574f25557d0f1bf9729d61dde9f44f1806d8ede
Date: Wed, 25 Nov 2015 13:47:57 +0100 [thread overview]
Message-ID: <20151125124757.36B1C21579@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 1574f25557d0f1bf9729d61dde9f44f1806d8ede (commit)
from 56b9e4553e150d514a47de1af7fae2abc43bdd0f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1574f25557d0f1bf9729d61dde9f44f1806d8ede
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Nov 25 12:47:29 2015 +0000
routing.cgi: Fix syntax error that caused an Internal Server Error
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/routing.cgi | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/routing.cgi b/html/cgi-bin/routing.cgi
index 2c60f67..7636d1e 100644
--- a/html/cgi-bin/routing.cgi
+++ b/html/cgi-bin/routing.cgi
@@ -118,10 +118,9 @@ if ($settings{'ACTION'} eq $Lang::tr{'toggle enable disable'}) {
}
if ($settings{'ACTION'} eq $Lang::tr{'add'}) {
-
# Validate inputs
- if (!&General::validipandmask($settings{'IP'}))){
- $errormessage = $Lang::tr{'invalid ip'}." / ".$Lang::tr{'invalid netmask'};
+ if (!&General::validipandmask($settings{'IP'})){
+ $errormessage = $Lang::tr{'invalid ip'}." / ".$Lang::tr{'invalid netmask'};
}else{
#set networkip if not already correctly defined
my($ip,$cidr) = split(/\//,$settings{'IP'});
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-11-25 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151125124757.36B1C21579@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox