| commit | 48f60345a8fecdd9aa037ca0e472edabaab9ff36 | [log] [tgz] |
|---|---|---|
| author | Naomi Seyfer <naomi@seyfer.org> | Fri Jun 15 11:44:17 2018 -0700 |
| committer | Vilas Jagannath <vilasj@google.com> | Fri Jun 15 14:44:17 2018 -0400 |
| tree | 87a80d2a7f46686950d9cd6122e4ac3c6be2ef2c | |
| parent | 9d32a1acd62bf0fae752bf7d83c5c4fba34e0173 [diff] |
Include 201 CREATED in HTTP success response codes (#237) * Include 201 CREATED in HTTP success response codes Previously, we only accepted 200 OK and 204 NO_CONTENT. Some APIs we'd like to use this library with return 201 CREATED when creating a resource, so that should also count as success (and behave like 200 OK).