Unbound advanced Invoming TCP Buffers validation

There is a variable cut-paste error here. Actually it never makes any difference in practice because outgoing_num_tcp and incoming_num_tcp are both set, so the logic comes out the same.
I noticed this while reviewing stuff in master for 2.3-ALPHA - might as well back-port stuff like this so that nobody who notices will worry about it in RELENG_2_2.
This commit is contained in:
Phil Davis 2015-11-10 11:23:57 +05:45
parent 7b41790bc7
commit f3d64bb5ee

View File

@ -100,7 +100,7 @@ if ($_POST) {
if (isset($_POST['outgoing_num_tcp']) && !in_array($_POST['outgoing_num_tcp'], array('0', '10', '20', '30', '40', '50'), true)) {
$input_errors[] = "A valid value must be specified for Outgoing TCP Buffers.";
}
if (isset($_POST['outgoing_num_tcp']) && !in_array($_POST['incoming_num_tcp'], array('0', '10', '20', '30', '40', '50'), true)) {
if (isset($_POST['incoming_num_tcp']) && !in_array($_POST['incoming_num_tcp'], array('0', '10', '20', '30', '40', '50'), true)) {
$input_errors[] = "A valid value must be specified for Incoming TCP Buffers.";
}
if (isset($_POST['edns_buffer_size']) && !in_array($_POST['edns_buffer_size'], array('512', '1480', '4096'), true)) {