Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 347 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

REST API - general question

dirkkotte

Hi all,

I got some problems after activating a FW rule via REST-API.
It seems as if all "fields" not passed in the request are set with default values !?
A simple "enable" of a rule (code see below) seems to set many other fields SRC-IP / DST-IP / SRV-Srevice / DST-Service to standard values (ANY).
With this the whole network was "switched off"
Are my observations correct?
Is it wanted like that? Is that "by design"?

192.168.10.254:4444/.../APIController operation="update"><FirewallRule><Name>DENY-Inetrnet-TestHost</Name><Status>Enable</Status><PolicyType>Network</PolicyType></FirewallRule></Set></Request>

Thanks in advance,

Dirk



This thread was automatically locked due to age.
Parents
  • +1

    Generelly speaking, the XML API requires all needed inputs, not only the changed one. If some parameters are missing, it will autofill or fail the transaction.

    This is not a RESTful API, instead a XML API, which replaces the values of the Object. 

    Basically my advice would be, simply query the object first, store the information in a array and replace the desired value in the array. Then push the entire object. 

Reply
  • +1

    Generelly speaking, the XML API requires all needed inputs, not only the changed one. If some parameters are missing, it will autofill or fail the transaction.

    This is not a RESTful API, instead a XML API, which replaces the values of the Object. 

    Basically my advice would be, simply query the object first, store the information in a array and replace the desired value in the array. Then push the entire object. 

Children
No Data