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.

Sign up for GitHub

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

Jump to bottom

RESTCONF: HTTP return codes are not according to RFC 8040 #56

Closed
achernavin22 opened this issue Nov 9, 2018 · 1 comment
Closed

RESTCONF: HTTP return codes are not according to RFC 8040 #56

achernavin22 opened this issue Nov 9, 2018 · 1 comment
Labels
bug

Comments

@achernavin22
Copy link

Ref: https://tools.ietf.org/html/rfc8040#section-4

For instance, the PUT request might return "201 Created" or
"204 No Content". For now, it always returns "200 OK" if successful.
olofhagsand added a commit that referenced this issue Jul 25, 2019
@olofhagsand
* RESTCONF PUT/POST erroneously returned 200 OK. Instead restconf now…
c1bae27 
… returns:

  * `201 Created` for created resources
  * `204 No Content` for replaced resources.
  * See [RESTCONF: HTTP return codes are not according to RFC 8040](#56)

* HTTP `Location:` fields added in RESTCONF POST replies
@olofhagsand
Copy link
Member

Fixed (finally) by commit^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olofhagsand @achernavin22