Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

copy-config: accepting same target as source #4

Closed
GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment
Closed

copy-config: accepting same target as source #4

GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Connect to server.
2. Send message with equal source and target datastore, for example:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="35">
  <copy-config>
        <source>
                <candidate/>
        </source>
        <target>
                <candidate/>
        </target>
</copy-config>
</rpc>


What is the expected output?
If the <source> and <target> parameters identify the same URL or
configuration datastore, an error MUST be returned with an error-
tag containing "invalid-value". [RFC6241]

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="35">
  <rpc-error>
    <error-tag>invalid-value</error-tag>
    <error-type>protocol</error-type>
    <error-severity>error</error-severity>
    <error-message>The request specifies an unacceptable value for one or more parameters.</error-message>
  </rpc-error>
</rpc-reply>

What do you see instead?

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="35">
  <ok/>
</rpc-reply>


Please use labels and text to provide additional information.


Original issue reported on code.google.com by david.kupka@gmail.com on 17 Oct 2012 at 1:11

@GoogleCodeExporter
Copy link
Author

This issue was closed by revision 3268ded0f461.

Original comment by rkre...@cesnet.cz on 17 Oct 2012 at 2:11

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant