当前位置：文江博客话题详情

PUT 和 POST 请求是否需要/期望有请求正文？

发布于 2024-12-03 00:06:15 字数 505 浏览 1 评论 0原文

我正在编写一个 RESTful api，并且正在考虑用户创建密钥的过程。我有以下可能性：

GET 请求 /new/ - 虽然这很容易，但我想我不会使用它，因为我听说 GET 用于检索和/或列出信息；
对 / 的 POST 请求 - 在我看来，这似乎足够简单，但不会在请求正文中传递任何数据。我可以这样做吗？这很奇怪吗？
POST 请求到 /keys 并传入请求正文 "keyname=SomeKey" - 这是正确的方法吗？

我查看了来自 Joyent 的 API，在所有 PUT 和 POST 请求中，它们在请求正文中传递了一些数据。这是预期的吗？在 PUT 和 POST 请求中不要求请求正文真的是错误的吗？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

你是我的挚爱i 2024-12-10 00:06:15

我在 Http-WG 上问了这个问题。这是我得到的最准确的答案：

需要注意的是，没有正文的消息仍然可以携带表示，因为表示是正文（长度可以为零）和标头的组合。
参见：
http://tools.ietf.org/ html/draft-ietf-httpbis-p3-payload-11#section-4

https://lists.w3.org/Archives/Public/ ietf-http-wg/2010JulSep/0276.html

总之，POST 不需要正文。我希望同样的理由也适用于 PUT。

回复收藏 0 原文

哥，最终变帅啦 2024-12-10 00:06:15

RFC2616 是 HTTP 1.1 的基础 RFC

在最常见的形式中，HTTP 消息是这样的（注意可选正文）：

generic-message = start-line
                  *(message-header CRLF)
                  CRLF
                  [ message-body ]
start-line      = Request-Line | Status-Line

进一步阅读会得出：

9.5 POST

   The POST method is used to request that the origin server accept the
   entity enclosed in the request as a new subordinate of the resource
   identified by the Request-URI in the Request-Line. ...

POST

9.6 PUT

   The PUT method requests that the enclosed entity be stored under the
   supplied Request-URI. ...

   The fundamental difference between the POST and PUT requests is
   reflected in the different meaning of the Request-URI. The URI in a
   POST request identifies the resource that will handle the enclosed
   entity. That resource might be a data-accepting process, a gateway to
   some other protocol, or a separate entity that accepts annotations.
   In contrast, the URI in a PUT request identifies the entity enclosed
   with the request -- the user agent knows what URI is intended and the
   server MUST NOT attempt to apply the request to some other resource.

和 PUT 都包含短语请求中包含的实体。

根据我的阅读，我相信 POST 和 PUT 都需要一个主体（我知道这是一个非规范的描述）。

在 REST 上下文中，POST 是创建，PUT 是更新。我可以想象创建一个空对象（也许是未来信息的占位符），但我不认为空更新有多大用处。

RFC2616 is the base RFC for HTTP 1.1

In the most general form, an HTTP message is this (note the optional body):

generic-message = start-line
                  *(message-header CRLF)
                  CRLF
                  [ message-body ]
start-line      = Request-Line | Status-Line

Reading further gives this:

9.5 POST

   The POST method is used to request that the origin server accept the
   entity enclosed in the request as a new subordinate of the resource
   identified by the Request-URI in the Request-Line. ...

and

9.6 PUT

   The PUT method requests that the enclosed entity be stored under the
   supplied Request-URI. ...

   The fundamental difference between the POST and PUT requests is
   reflected in the different meaning of the Request-URI. The URI in a
   POST request identifies the resource that will handle the enclosed
   entity. That resource might be a data-accepting process, a gateway to
   some other protocol, or a separate entity that accepts annotations.
   In contrast, the URI in a PUT request identifies the entity enclosed
   with the request -- the user agent knows what URI is intended and the
   server MUST NOT attempt to apply the request to some other resource.

Both POST and PUT include the phrase entity enclosed in the request.

Based on my reading, I believe that a body is desired (a non-normative description, I know) for both POST and PUT.

In the context of REST, POST is create and PUT is update. I can imagine creating an empty object (perhaps a placeholder for future information), but I don't imagine much use of an empty update.

回复收藏 0 原文