Cutting-off Prevention

In some cases you are required to call methods Session.getConfigTimestamp and Session.confirmConfig in order to confirm you are still able to connect to firewall with new configuration. This mechanism protects you from cutting yourself from the firewall. Otherwise your changes will be lost after 30 seconds automatically.

Example

Request:  {"jsonrpc":"2.0","id":1,"method":"TrafficPolicy.set","params":{ ... }}
Response: {"jsonrpc":"2.0","id":1,"result":{"errors":[]}}

Request:  {"jsonrpc":"2.0","id":2,"method":"Session.getConfigTimestamp"}
Response: {"jsonrpc":"2.0","id":2,"result":{"clientTimestampList":[{"name":"config","timestamp":517}]}}

Request:  {"jsonrpc":"2.0","id":3,"method":"Session.confirmConfig","params":{"clientTimestampList":[{"name":"config","timestamp":517}]}}
Response: {"jsonrpc":"2.0","id":3,"result":{"confirmed":true}}

List of Methods

Following methods uses the cutting off protection:

• BandwidthManagement.set
• BandwidthManagement.setBandwidth
• ConnectivityAssistant.set
• ContentFilter.set
• Dhcp.apply
• Domains.apply
• Interfaces.apply
• IpAddressGroups.apply
• IpServices.apply
• P2pEliminator.set
• Ports.set
• ReverseProxy.set
• RoutingTable.setStaticRoutes
• SecuritySettings.set
• TimeRanges.apply
• TrafficPolicy.set
• UrlGroups.apply
• Users.set
• Users.remove
• UserGroups.set
• UserGroups.remove
• VpnRoutes.apply
• WebInterface.set