[fix] don't fail if the content type JSON is not specified in the request#146
Merged
Ramon-Jimenez merged 1 commit intodevelopmentfrom Jun 11, 2025
Merged
Conversation
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
2 participants
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.
Fixes https://app.clickup.com/t/8699cygm6
The transition from Flask v2 to v3 broke the proxy between the API and Harbor. Flask now explicitly validates that the
Content-Typeheader is set toapplication/jsonbefore attempting to parse the request body as JSON.To avoid requiring changes in clients — and since our API consistently uses JSON — we've added the
force=Trueflag when parsing request bodies.