Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Pricing
Podcast Image

リファクタリングとともに生きるラジオ

#59 更新系API① POST/PUTのレスポンスどうする?

27 Jan 2025

Description

■ トピック shinshinさんからのおたより 寿司回で気になっていた、POST/PUTのレスポンスについて If one or more resources has been created on the origin server as a result of successfully processing a POST request, the origin server SHOULD send a 201 (Created) response containing a Location header field that provides an identifier for the primary resource created and a representation that describes the status of the request while referring to the new resource(s). アプリケーションで使わないレスポンスの必要性 イミュータブルな単方向データフローにしたい 富豪的プログラミング Responses to POST requests are only cacheable when they include explicit freshness information and a Content-Location header field that has the same value as the POST's target URI. POSTのキャッシュ可能性 Webブラウザのために仕様に準拠する PUTの話 If the target resource does have a current representation and that representation is successfully modified in accordance with the state of the enclosed representation, then the origin server MUST send either a 200 (OK) or a 204 (No Content) response to indicate successful completion of the request. PUTのレスポンスはキャッシュできない SHOULDでも従っておいたほうがよさそう 内容に間違いがあることを前提に聞いてください 次回はリクエストのスキーマについて ■ 参考リンク RFC 9110 - HTTP Semantics RFC 9110 — HTTP Semantics (日本語訳) ■ おたよりフォーム https://forms.gle/RYUG7T4ctmF7Srf36 ■ X(Twitter) https://twitter.com/refactoradio ■ Bluesky https://bsky.app/profile/refactoradio.com ハッシュタグは #リファラジ です。

Audio
Featured in this Episode

No persons identified in this episode.

Transcription

This episode hasn't been transcribed yet

Help us prioritize this episode for transcription by upvoting it.

0 upvotes
🗳️ Sign in to Upvote

Popular episodes get transcribed faster

Comments

There are no comments yet.

Please log in to write the first comment.