Skip to content

Fix content type for dynamic client registration#101

Open
ioweb-gr wants to merge 1 commit intohyprmcp:mainfrom
ioweb-gr:fix/dcr-content-type
Open

Fix content type for dynamic client registration#101
ioweb-gr wants to merge 1 commit intohyprmcp:mainfrom
ioweb-gr:fix/dcr-content-type

Conversation

@ioweb-gr
Copy link

This pull request makes a minor adjustment to the HTTP response handling in the NewDynamicClientRegistrationHandler function. The order of setting the Content-Type header and writing the status code is corrected to ensure proper HTTP response formatting.

Copilot AI review requested due to automatic review settings March 14, 2026 22:14
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adjusts the dynamic client registration HTTP response to ensure headers are set correctly before writing the status code, so clients reliably receive Content-Type: application/json on successful registration responses.

Changes:

  • Set Content-Type header before calling WriteHeader(http.StatusCreated) in the registration handler.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

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