From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 07805a0e6353cad46148976484427264cbc268c6
Date: Wed, 27 May 2026 15:43:20 +0000 (UTC) [thread overview]
Message-ID: <4gQYmm25Btz2xKs@people01.haj.ipfire.org> (raw)
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, next has been updated
via 07805a0e6353cad46148976484427264cbc268c6 (commit)
from b4ce17172bbe95777498d663a202d056ee45af44 (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 07805a0e6353cad46148976484427264cbc268c6
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Wed May 27 16:42:50 2026 +0100
firewall.cgi: Don't try to encode the remarks on save
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/firewall.cgi | 3 ---
1 file changed, 3 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/firewall.cgi b/html/cgi-bin/firewall.cgi
index 20e6a95e4..8900c4fae 100644
--- a/html/cgi-bin/firewall.cgi
+++ b/html/cgi-bin/firewall.cgi
@@ -2349,9 +2349,6 @@ sub saverule
#print"6";
}
$fwdfwsettings{'ruleremark'}=~ s/,/;/g;
- utf8::decode($fwdfwsettings{'ruleremark'});
- $fwdfwsettings{'ruleremark'}=&Header::escape($fwdfwsettings{'ruleremark'});
- $fwdfwsettings{'PROT'}=&Header::escape($fwdfwsettings{'PROT'});
if ($fwdfwsettings{'updatefwrule'} ne 'on'){
my $key = &General::findhasharraykey ($hash);
$$hash{$key}[0] = $fwdfwsettings{'RULE_ACTION'};
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-27 15:43 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=4gQYmm25Btz2xKs@people01.haj.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