Comments (1)
Small update to this since I've received a few duplicates of this issue. This occurs because pfSense only parses the XML configuration as strings and arrays of strings. This prevents values from returning in the format accepted by the API. Additionally, if updating or interacting with a stored object such as a PUT request to the /api/v1/firewall/rule endpoint, data processed/validated during the API call will be returned as the accepted format whereas the stored/untouched data will remain a string as parsed by pfSense. This creates mismatches in return data. An API representation component will need to be incorporated into the API framework to act as a translation piece between the pfSense expected/stored data and the API data.
This will be a very large change that is unlikely to happen anytime soon. For now, it is best to make your scripts aware of this issue and always check/convert data types when it is returned by the API and before any returned data is sent back to the API if they are needed as a specific type.
from pfsense-api.
Related Issues (20)
- Is it me or API token authentication is broken in pfsense 2.7.0? HOT 3
- API authentication JWT does not work with none admin users HOT 1
- /api/v1/firewall/nat/outbound/mapping throws error when no mappings exist
- API version compare returns always "update_available" false HOT 1
- Captive Portal API HOT 2
- Error when updating firewall alias
- Alias description is blank if its the first alias on the list HOT 1
- Put method on /api/v1/user got HTTP 405 error HOT 1
- Be able to create token to an other user from admin
- PUT system/config not working. Unable to write config HOT 5
- bad request 4031 Firewall rule tracker ID required HOT 1
- pfSense API not able to logon to pfSense after upgrade to version 2.7 HOT 2
- /api/v1/firewall/nat/outbound/mapping `target` field no longer works correctly on pfSense 2.7.1
- Plus: Support CARP Unicast mode
- FreeRadius Configuration HOT 1
- Crash report HOT 3
- 2.0.0 package for pfSense 23.09 HOT 1
- Crash in v2.0.0 HOT 3
- pfsense-api environment crash can still submit a post but the gui can't see the result HOT 2
- POST | IPsec Phase2 | "hash-algorithm-option" is required even for GCM Algorithms HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pfsense-api.