Skip to content

fix: correct success status codes on Management Interface endpoints#196

Open
matlec wants to merge 1 commit into
pre-draftfrom
fix/capabilities-http-status
Open

fix: correct success status codes on Management Interface endpoints#196
matlec wants to merge 1 commit into
pre-draftfrom
fix/capabilities-http-status

Conversation

@matlec

@matlec matlec commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Description

This is a spec hygiene fix.

The Device Capabilities endpoint documented 201 OK for every successful write. That reason phrase does not exist (201 is Created, 200 is OK), and a single 201 was used for both creating and updating a document. Per RFC 9110, 201 Created is correct only when a new resource is created. An update should return 200 OK. This meant a client updating an device that was already registered received 201, reporting a creation that never happened.

This PR aligns the Management Interface endpoints on a single convention: 201 Created on creation, 200 OK on update, 204 No Content on delete.

Issues Addressed

#195

Change Type

Please select the relevant options:

  • Fix (change that resolves an issue)
  • New enhancement (change that adds specification content)
  • Content edits (change that edits existing content)

Checklist

  • I have read the CONTRIBUTING document.
  • My changes adhere to the established patterns, and best practices.

This resolves #195.

Signed-off-by: Matthias Lechner <matlec.public@gmail.com>
@matlec
matlec requested a review from a team as a code owner July 21, 2026 07:23
@phil-abb
phil-abb self-requested a review July 21, 2026 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants