Skip to content

fix: Add 201 as allowed response to PUT#97

Merged
egrimstad merged 1 commit intomainfrom
fix/PUT-201
Mar 10, 2026
Merged

fix: Add 201 as allowed response to PUT#97
egrimstad merged 1 commit intomainfrom
fix/PUT-201

Conversation

@egrimstad
Copy link
Contributor

HTTP standard indicates that PUT can return 201: https://www.rfc-editor.org/rfc/rfc9110.html#name-put

If the target resource does not have a current representation and the PUT successfully creates one, then the origin server MUST inform the user agent by sending a 201 (Created) response.

HTTP standard indicates that PUT can return 201: https://www.rfc-editor.org/rfc/rfc9110.html#name-put

> If the target resource does not have a current representation and the PUT successfully creates one, then the origin server MUST inform the user agent by sending a 201 (Created) response.
@egrimstad egrimstad requested a review from a team as a code owner March 3, 2026 13:42
@egrimstad egrimstad merged commit 3ac6331 into main Mar 10, 2026
3 checks passed
egrimstad pushed a commit that referenced this pull request Mar 10, 2026
🤖 I have created a release *beep* *boop*
---


##
[2.2.2](v2.2.1...v2.2.2)
(2026-03-10)


### Bug Fixes

* Add 201 as allowed response to PUT
([#97](#97))
([3ac6331](3ac6331))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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