Actions
Regression #15158
openXMLRPC Timeout won't save if over 150
Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
Firewall/pfBlockerNG/Sync has option "XMLRPC Timeout":
<input class="form-control" name="varsynctimeout" id="varsynctimeout" type="number" value="150" min="0" max="5000" step="50" placeholder="Enter timeout in seconds">
If one sets the spinner a number higher than 150 the value is saved at 150. Ergo no value over 150 is allowed.
Updated by Danilo Zrenjanin 11 months ago
- Status changed from New to Confirmed
Tested against:
23.09.1-RELEASE (amd64) built on Wed Dec 20 18:27:00 UTC 2023 FreeBSD 14.0-CURRENT
pfBlockerNG net 3.2.0_7
I was able to replicate the reported issue.
Updated by dylan mendez 9 months ago
I was able to replicate this on 24.03.b.20240311.0600, pfBlockerNG 3.2.0_8
Updated by dylan mendez 6 months ago
Still able to replicate this on 24.08.a.20240702.0600 pfBlocker version 3.2.0_13
Updated by Danilo Zrenjanin 28 days ago
The issue persisted in pfBlocker 3.2.0_20
I tested against pfSense Plus 24.03.
Actions