Bug #2374
When entering values in firewall rules leading and trailing spaces are not deleted
| Status: | Feedback | Start date: | 04/13/2012 | |
|---|---|---|---|---|
| Priority: | Very Low | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Web Interface | |||
| Target version: | - | |||
| Affected version: | 2.0.1 | Affected Architecture: | All |
Description
Hi,
as the topic says. If you enter a port number in the firewall rules page and you add a leading or trailing space by mistake the system complaints about this and says that the number is not a valid portnumber.
As one can't see the space in the error message it's kinda tricky.
I added a screenshot to show the problem. The trailing space is at the end of the destination port range's end number.
Automagic format or something would be nice.
KR,
Grimeton
Associated revisions
Fix of bug #2374 "When entering values in firewall rules leading and
trailing spaces are not deleted"
History
#1
Updated by Jim P about 1 year ago
- Subject changed from When entering port numbers in firewall rules leading and trailing spaces are not deleted to When entering values in firewall rules leading and trailing spaces are not deleted
Same thing happens for IPs also. Shouldn't be too hard to trim() before checking though.