Feature #15276
open
Support JSON content for URL type firewall aliases
0%
Description
Brilliant pfSense DevTeam!
WHERE
In Firewall / Aliases, URLs tab(selector)
CASE
JSON need to be allowed in “URL (IPs)” type of firewall aliases, the same as XML and TXT are allowed.
ARGUMENT
Nowadays most SaaS and services present their data on JSON and XML more frequently than PLAIN TXT file answer on certain URL.
(For example external monitoring services.)
And logically wrong if pfSense user able to entering the XML and PLAIN TXT source in URL (IPs), but no JSON. (And only URL Table (IPs) allow the JSON).
I understand that from the beginning of pfSense’s life exist only 2 types of URL-sources:
- small lists
- big lists
and to eliminate time and resources to keep IPs, the parameter/ability of refresh of big lists was made in WebGUI.
But FROM USERS PERSPECTIVE all 3(JSON, XML and PLAIN TXT) source are the same - certain amount of data, and frustrating when possible to add XML and PLAIN TXT in URL (IPs), but JSON - only in another type, only in URL Table (IPs).
Thank You!
Updated by Jim Pingle 2 months ago
- Tracker changed from Bug to Feature
- Subject changed from JSON need to be allowed in “URL (IPs)” type of firewall aliases to Support JSON content for URL type firewall aliases
- Priority changed from Normal to Very Low
- Affected Version deleted (
All) - Affected Architecture deleted (
All)
Not a bug, it's a feature request.
Not sure how viable it would be as there isn't really a standard for that and who knows if any two different feed publishers would use the same JSON structure. Plain text is universal.