* Netconf as default namespace has been disabled by default.
* Only requests on the form: `<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><edit-config>...` will be accepted * All replies will be on the form: `<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">...` * Requests such as: `<rpc><edit-config>...` will not be accepted. * You can revert this behaviour (to clixon pre-4.6 behaviour) by enabling `CLICON_NAMESPACE_NETCONF_DEFAULT` * This API change is a consequence of: [copy-config's RPC cxobj parameter does not contain namespace #131](https://github.com/clicon/clixon/issues/131)
This commit is contained in:
parent
a01fe04613
commit
81fc7f742b
81 changed files with 976 additions and 830 deletions
|
|
@ -47,14 +47,6 @@
|
|||
*/
|
||||
#undef RPC_USERNAME_ASSERT
|
||||
|
||||
/* If rpc call does not have a namespace (eg using xmlns) then use the default
|
||||
* NETCONF namespace (see rfc6241 3.1)
|
||||
* Undefine it if you want to ensure strict namespace assignment on all netconf and
|
||||
* XML statements.
|
||||
* The base namespace is defined as NETCONF_BASE_NAMESPACE
|
||||
*/
|
||||
#define USE_NETCONF_NS_AS_DEFAULT
|
||||
|
||||
/*! Tag for wrong handling of identityref prefixes (XML encoding)
|
||||
* See https://github.com/clicon/clixon/issues/90
|
||||
* Instead of using generic xmlns prefix bindings, the module's own prefix
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue