fix: 405 instead of 501 on POST to v1 detail API#11162
Merged
jennifer-richards merged 3 commits intoJul 6, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #11162 +/- ##
==========================================
+ Coverage 88.52% 88.58% +0.06%
==========================================
Files 334 333 -1
Lines 45102 44665 -437
==========================================
- Hits 39927 39568 -359
+ Misses 5175 5097 -78 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
rjsparks
approved these changes
Jul 6, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This will prevent 501 errors on POST to API v1 routes like
/api/v1/submit/submission/auth/. Note that there's nothing special about that app/model or the/auth/there - we get the same response for/api/v1/doc/document/frobozz/zorkmid/.This is a narrow fix, specifically handling the
post_detailview. We could consider wholesale blocking of POST/PATCH/PUT/DELETE to the v1 API, but that will require touching all of our resource classes to limit the allowed methods (at least for the straightforward mechanism, there may be cleverer approaches).