Repository navigation
fix(api): accept JSON bodies regardless of content type - #14
Merged
Merged
Conversation
KAJdev
marked this pull request as ready for review
November 11, 2026 21:59
justinwlin
self-requested a review
November 12, 2026 01:15
justinwlin
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Calling a native API route with
curl -X POST https://<worker>/echo -d '{"prompt":"hi"}'could return HTTP 422 because curl labels the JSON as form data. Native body handlers parse one complete JSON object regardless of the content-type header, so this request reaches the handler as{"prompt": "hi"}.Missing, malformed, null, and non-object bodies return HTTP 422 before the handler runs. Native routes advertise their required JSON-object body in OpenAPI.
Fixes CON-2064